Systems and methods for assessing turns made by a vehicle

ABSTRACT

Various embodiments of the present invention are generally directed to a systems and methods for assessing turns made by one or more vehicles. According to various embodiments, the system is configured to identify, based telematics data captured from the vehicles, turns executed by the vehicle during a particular time period. The system is further configured to analyze the identified turns to determine and display various turn segment attributes to a user in order to provide an indication of turns having an abnormal or excessive duration and/or to provide overall efficiency-indicative information relating to the vehicle turns.

BACKGROUND OF THE INVENTION

Field of the Invention

Various embodiments of the present invention described herein generallyrelate to efficiency management systems for identifying and analyzingturns made by at least one vehicle.

Description of Related Art

Improving operational efficiency has become an increasingly highpriority for many businesses. In particular, the increasing cost ofenergy resources, such as fuel, and recent trends toward improvingenvironmental sustainability have made reducing the consumption ofenergy resources essential for many businesses to maintain a competitiveadvantage in their respective industries. Likewise, volatile economicclimates have increased competition in various industry sectors andprompted competing businesses to provide better services at a lowercost. As a result, many businesses are searching for ways to improvetheir operational efficiency in order to reduce costs and provideimproved service to customers.

As business emphasis on operational efficiency has grown, so too has thedevelopment of technology capable of monitoring various operationalcharacteristics. For example, businesses can use GPS (or other GNSSsystems) and RFID technology to track the location of people, vehicles,and items and generate data representative of those locations inrelation to time. In addition, telematics devices are currently used invehicles to capture information relating to various vehicle dynamics,such as fuel consumption and location.

Although such technology allows businesses to capture large amounts ofoperational data reflecting a variety of operational characteristics,many businesses are unable to effectively utilize such data to improveefficiencies. This problem is commonly the result of an inability toeffectively translate otherwise overwhelming amounts of data into aformat that is meaningful in the context of analyzing a particularefficiency. Thus, there is a need in the art for improved systems andmethods for capturing and evaluating operational data in order toimprove operational efficiencies in a variety of business contexts.

BRIEF SUMMARY OF THE INVENTION

Various embodiments of the present invention are generally directed to asystem for assessing turns made by at least one vehicle. According tovarious embodiments, the system comprises one or more memory storageareas; and one or more processors in communication with said one or morememory storage areas. The processors are, collectively, configured to:receive vehicle telematics data indicative of a travel path of thevehicle during one or more time periods; identify, based at least inpart on said vehicle telematics data, one or more turns executed by thevehicle during the one or more time periods, the one or more turns eachcomprising instances in which the vehicle executes a turn in order tochange from (i) traveling in a first roadway direction on a first roadto (ii) traveling on a second road or traveling in a second roadwaydirection on the first road; and determine for each identified turn aturn segment comprising a beginning turn point and an ending turn point,the time elapsed between the beginning turn point and ending turn pointdefining the duration of the turn segment.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is a block diagram of an efficiency management system accordingto one embodiment of the present invention;

FIG. 2 is a block diagram of a fleet management system according to oneembodiment of the present invention;

FIG. 3 is a block diagram of a telematics device according to oneembodiment of the present invention;

FIG. 4 is a schematic block diagram of a central server according to oneembodiment of the present invention;

FIG. 5 is a flow diagram of steps executed by the telematics deviceaccording to one embodiment of the present invention;

FIG. 6 is a flow diagram of steps executed by a turn segment moduleaccording to one embodiment of the present invention;

FIG. 7 is a diagram of data points captured by the telematics device asa vehicle executes a right-hand turn at an intersection of roadsaccording to one embodiment;

FIG. 8 is a Gantt chart display of a vehicle turn segment associatedwith the turn shown in FIG. 7 according to one embodiment;

FIG. 9 shows a start-up view of a graphical user interface according toone embodiment of the present invention;

FIG. 10 shows exemplary steps executed by a central server in order torespond to user evaluation requests received via a user interfaceaccording to one embodiment of the present invention;

FIG. 11 shows exemplary steps executed by an outlier report moduleaccording to one embodiment of the present invention;

FIG. 12 shows an outlier report graphical user interface according toone embodiment of the present invention;

FIG. 13 shows exemplary steps executed by a summary report moduleaccording to one embodiment of the present invention;

FIG. 14 shows a summary report graphical user interface according to oneembodiment of the present invention;

FIG. 15 shows exemplary steps executed by a turn by turn analysis moduleaccording to one embodiment of the present invention;

FIGS. 16 and 17 show turn by turn graphical user interfaces according toone embodiment of the present invention;

FIG. 18 shows exemplary steps executed by a turn type analysis moduleaccording to one embodiment of the present invention;

FIG. 19 shows a turn type graphical user interface according to oneembodiment of the present invention;

FIG. 20 shows exemplary steps executed by an intersection type analysismodule according to one embodiment of the present invention;

FIG. 21 shows an intersection type graphical user interface according toone embodiment of the present invention;

FIG. 22 shows exemplary steps executed by an intersection point analysismodule according to one embodiment of the present invention; and

FIG. 23 shows an intersection point analysis graphical user interfaceaccording to one embodiment of the present invention.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

The present invention will now be described more fully hereinafter withreference to the accompanying drawings, in which some—but notall—embodiments of the invention are shown. Indeed, this invention maybe embodied in many different forms and should not be construed aslimited to the embodiments set forth herein; rather, these embodimentsare provided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

Many modifications and other embodiments of the invention set forthherein will come to mind to one skilled in the art to which thisinvention pertains having the benefit of the teachings presented in thedescriptions herein and the associated drawings. Therefore, it is to beunderstood that the invention is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

Overview

According to various embodiments of the present invention, an efficiencymanagement system is provided for evaluating various operationalefficiencies based on operational data. FIG. 1 illustrates thehigh-level system architecture of an efficiency management system 1according to various embodiments. As shown, the efficiency managementsystem 1 includes one or more data sources 2 and a central server 3. Thedata sources 2 may be, for example, devices configured for capturing andcommunicating operational data indicative of one or more operationalcharacteristics (e.g., a telematics device capturing telematics datafrom a vehicle). The data sources 2 are configured to communicate withthe central server 3 by sending and receiving operational data over anetwork 4 (e.g., the Internet, an Intranet, or other suitable network).The central server 3 is configured to process and evaluate operationaldata received from the data sources 2 in accordance with user inputreceived via a user interface (e.g., a graphical user interface providedon a local or remote computer). For example, in certain embodiments, thecentral server 3 is configured for segmenting operational data accordingto various operational activities, identifying various undesirable orinefficient activities or occurrences based on the operational data,and/or generating a graphical presentation based on the operational datathat displays operational activities in the context of otherefficiency-indicative data.

As discussed in greater detail below, the components and general systemarchitecture of the efficiency management system 1 illustrated in FIG. 1may be adapted for use in specific environments. For example, in certainembodiments, the efficiency management system is configured as a “fleetmanagement system” adapted for evaluating and managing a fleet ofvehicles (e.g., a fleet of delivery vehicles operated by a shippingentity, a fleet of taxis or buses operated by a private or publictransportation entity). In such embodiments, the data sources maycomprise telematics devices positioned on various vehicles in the fleet,as well as mobile service devices operated at least in part by operatorsof the fleet vehicles. Likewise, the central server may be configuredfor evaluating telematics data received from the telematics devices inorder to assess vehicle efficiency and other logistical efficiencies. Inaddition, the central server may be configured for providing graphicalpresentations of telematics data in efficiency-indicative formats, aswell as for updating GPS-based maps based on vehicle telematics data.

The following description provides a detailed explanation of certainembodiments of the efficiency management system, including theaforementioned fleet management system. As will be appreciated from thedetailed description herein, the various components and features ofthese systems may be modified and adapted to assess efficiencies in avariety of operational contexts.

Fleet Management System

According to various embodiments, a fleet management system is providedfor capturing and storing operational data for a fleet of vehicles, andfor evaluating the operational data in order to assess various fleetefficiencies and improve the overall operational efficiency of thefleet. The fleet management system may be used, for example, by ashipping entity (e.g., United Parcel Service, Inc., FedEx Corp., or theUnited States Postal Service) to evaluate the efficiency of a fleet ofvehicles used to deliver freight or packages. As described in detailbelow, various embodiments of the fleet management system are configuredto capture operational data from the fleet—including telematics datafrom fleet vehicles—and evaluate the captured operational data in orderto identify inefficient operations. As a particular example, theefficiency management system is configured to evaluate telematics datacaptured from one or more vehicles to evaluate the operationalefficiency of turns made by a vehicle during a particular time period,along a particular travel route, and/or within a particular geographicarea. As will be appreciated from the description herein, this and othersystem attributes allow the fleet management system to assist vehiclefleet managers (e.g., shipping entities) in improving the operatingefficiency of their fleet.

Fleet Management System Architecture FIG. 2 shows the systemarchitecture of a fleet management system 5 according to variousembodiments. In the illustrated embodiment, the fleet management system5 comprises a vehicle telematics device 102 positioned on a deliveryvehicle 100 and a central server 120. The telematics device 102 and thecentral server 120 are configured to communicate with each other via acommunications network 130 (e.g., the Internet, an Intranet, a cellularnetwork, or other suitable network). In addition, the telematics device102 and central server 120 are configured for storing data to anaccessible central server database (not shown) located on, or remotelyfrom, the central server 120.

In the description provided herein, the fleet management system 5 may beconfigured for managing and evaluating the operation of a large fleet ofdelivery vehicles. As such, in various embodiments, the fleet managementsystem 5 may further comprise a plurality of telematics devices 102,each being associated with one of a plurality of delivery vehicles 100.While the detailed description of the fleet management system'scomponents is provided below with reference to individual components ordevices, it will be understood from the description herein that variousembodiments of the fleet management system 5 may include a plurality ofthe components each configured as described below. For example,large-scale embodiments of the fleet management system may includethousands of telematics devices 102 each capturing data from a uniquedelivery vehicle 100 and transmitting the captured data to multipleservers 120. In addition, as will be appreciated from the descriptionherein, the fleet management system 5 may be adapted for managing andevaluating a fleet of vehicles in a variety of contexts, such as a fleetof taxis, buses, and other service vehicles. Accordingly, the telematicsdevice 102 represents one embodiment of a telematics device that may beadapted for providing telematics data for a fleet of vehicles.

In the illustrated embodiment of FIG. 2, the delivery vehicle 100includes a plurality of vehicle sensors configured for generatingtelematics data indicative of various vehicle dynamics, such as engineignition, engine speed, vehicle speed, vehicle location, vehicleheading, and the status of various vehicle components. The vehiclesensors may be controlled by the telematics device 102, which may bepositioned on or within the vehicle 100. In controlling the variousvehicle sensors, the telematics device 102 is able to capture and storetelematics data from the various vehicle sensors according to aprogrammed logic and associate the captured telematics data withcontextual data (e.g., date, time, location). The captured telematicsdata and contextual data may then be transmitted by the telematicsdevice 102 directly to the central server 120 via the network 130, or toanother computing device (which may later transmit the data to thecentral server 120 itself).

According to various embodiments, the central server 120 is generallyconfigured for evaluating operational data (e.g., telematics data) for afleet of vehicles in order to assess various fleet efficiencies and aidfleet management system 5 users in managing the fleet. As shown in FIG.2, the central server 120 may be configured for receiving and storingtelematics data from the telematics device 102 over the network 130. Bycollecting such operational data over a period of time from varioustelematics devices 102—which may be associated with a fleet of vehicles100—the central server 120 is able to amass operational data reflectingthe overall operations of the fleet. As will be described in greaterdetail below, the central server 120 may be configured for evaluatingtelematics data, presenting the data to a user, and evaluating the datain a variety of ways in order to improve the operating efficiency of thefleet of vehicles 100.

The various components of the fleet management system 5 are nowdescribed in detail below according to various embodiments.

Network

According to various embodiments of the present invention, thecommunications network 130 may be capable of supporting communication inaccordance with any one or more of a number of second-generation (2G),2.5G, third-generation (3G), and/or fourth-generation (4G) mobilecommunication protocols or the like. More particularly, the network 130may be capable of supporting communication in accordance with 2Gwireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA).Also, for example, the network 130 may be capable of supportingcommunication in accordance with 2.5G wireless communication protocolsGPRS, Enhanced Data GSM Environment (EDGE), or the like. In addition,for example, the network 130 can be capable of supporting communicationin accordance with 3G wireless communication protocols such as UniversalMobile Telephone System (UMTS) network employing Wideband Code DivisionMultiple Access (WCDMA) radio access technology. As yet another example,the network 130 may support communication between the fleet managementsystem 5 components (e.g., the telematics device 102) in accordance withtechniques such as, for example, radio frequency (RF), Bluetooth™,infrared (IrDA), or any of a number of different wireless networkingtechniques, including Wireless LAN (WLAN) techniques.

Vehicle Sensors

As noted above, in various embodiments the delivery vehicle 100 isequipped with a variety of vehicle sensors capable of generating vehicletelematics data. For example, in one embodiment, the vehicle 100includes sensors configured to make measurements and capture datapertaining to the following vehicle dynamics: engine ignition (e.g., onor off), engine speed (e.g., RPM and idle time events), vehicle speed(e.g., miles per hour), seat belt status (e.g., engaged or disengaged),vehicle heading (e.g., degrees from center), vehicle backing (e.g.,moving in reverse or not moving in reverse), vehicle door status (e.g.,open or closed), vehicle handle status (e.g., grasped or not grasped bya driver), vehicle location (e.g., GPS coordinates; latitude andlongitude), distance traveled (e.g., miles between two points), throttleposition, brake pedal position, parking brake position, distance or timesince last maintenance, and various engine measurements (e.g., engineoil pressure, engine temperature, and engine faults). In various otherembodiments, the delivery vehicle 100 may include any combination of theabove-referenced sensors (and additional sensors known in the art)depending on the operational data desired by a fleet management system 5user.

According to various embodiments, the vehicles sensors disposed withinthe delivery vehicle 100 comprise on/off sensors, which register avoltage amount that corresponds with an on/off condition. For example,in one embodiment, a seat belt sensor may register 0V when the seat beltis disengaged and 12V when the seat belt is engaged. Such on/off sensorsare sufficient for measuring vehicle dynamics in which operational datais needed to indicate two conditions, such as a seat belt, which iseither engaged or disengaged at all times. As another example, one ormore door position sensors may be connected, for example, to the driverside, passenger side, and bulkhead doors, and may register 0V when thedoor with which the sensor is associated is in an open position, and 12Vwhen the door is closed. As another example, an ignition sensor mayregister 0V when the vehicle 100 is turned off and 12V when the vehicle100 is turned on. As yet another example, a backing light sensor mayregister 0V when the vehicles' backing lights are off and 12V when thevehicle's backing lights are on. As yet another example, the engine idlesensor may be configured to generate 0V when the engine speed is aboveidle and 12V when the engine is idling.

In addition, according to various embodiments, the vehicle sensorsdisposed within the delivery vehicles 100 also comprise variable voltagesensors, which may be used to register variations in voltage reflectinga certain vehicle dynamic. For example, the engine speed sensor maydetect the speed of the engine in revolutions per minute (RPM) byregistering a particular voltage that corresponds to a particular RPMreading. The voltage of the sensor may increase or decreaseproportionately with increases or decreases in the engine RPM. Asanother example, oil pressure sensors may detect the vehicle's oilpressure by registering a particular voltage that corresponds to aparticular oil pressure. Other examples of variable voltage sensors mayinclude temperature sensors, vehicle speed sensors, vehicle headingsensors, and vehicle location sensors.

The exemplary vehicle sensors described above may be configured, forexample, to operate in any fashion suitable to generatecomputer-readable data that may be captured, stored, and transmitted bythe telematics device 102. In addition, while certain sensors arepreferably disposed at particular locations on or within the vehicles100 (e.g., handle sensors at the vehicle handles), other sensors may bedisposed anywhere within the vehicle, such as within the telematicsdevice 102 itself (e.g., a location sensor).

Telematics Device

As noted above, according to various embodiments, the telematics device102 is configured to control various vehicle sensors positioned on anassociated delivery vehicle 100, capture vehicle telematics datagenerated by those sensors, and transmit the captured telematics data tothe central server 120 via one of several communication methods.According to various embodiments, the various functions of thetelematics device 102 described herein may be generally understood asbeing performed by one or more of the telematics device 102 componentsdescribed below.

FIG. 3 illustrates a detailed schematic block diagram of an exemplarytelematics device 102 according to one embodiment. In the illustratedembodiment, the telematics device 102 includes the following components:a processor 201, a location-determining device or sensor 202 (e.g., GPSsensor), a real-time clock 203, J-Bus protocol architecture 204, anelectronic control module (ECM) 205, a port 206 for receiving data fromvehicle sensors 410 located in one of the delivery vehicles 100 (shownin FIG. 2), a communication port 207 for receiving instruction data, aradio frequency identification (RFID) tag 212, a power source 208, adata radio 209 for communication with a WWAN, a WLAN and/or a WPAN,FLASH, DRAM, and NVRAM memory modules 210, and a programmable logiccontroller (PLC) 211. In an alternative embodiment, the RFID tag 212,the location sensor 202, and the PLC 211 may be located in the deliveryvehicle 100, external from the telematics device 102. In otherembodiments, the processes described herein as being carried out by asingle processor 201 may be accomplished by multiple processors. Invarious embodiments, the telematics device 102 may not include certainof the components described above, and may include any other suitablecomponents in addition to, or in place of, those described above. Forexample, the telematics device 102 may include various types ofcommunications components other than those described above (e.g., tosupport new or improved communications techniques).

In one embodiment, the location sensor 202 may be one of severalcomponents available in the telematics device 102. The location sensor202 may be, for example, a GPS-based sensor compatible with a low Earthorbit (LEO) satellite system, medium Earth orbit satellite system, or aDepartment of Defense (DOD) satellite system. Alternatively,triangulation may be used in connection with various cellular towerspositioned at various locations throughout a geographic area in order todetermine the location of the delivery vehicle 100 and/or its driver.The location sensor 202 may be used to receive position, time, and speeddata. In addition, the location sensor 202 may be configured to detectwhen its delivery vehicle 100 has entered or exited a GPS-definedgeographic area (e.g., a geo-fenced area). As will be appreciated fromthe description herein, more than one location sensor 202 may beutilized, and other similar techniques may likewise be used to collectgeo-location information associated with the delivery vehicle 100 and/orits driver.

In one embodiment, the ECM 205 with J-Bus protocol 204 may be one ofseveral components available in the telematics device 102. The ECM 205,which may be a scalable and subservient device to the telematics device102, may have data processor capability to decode and store analog anddigital inputs and ECM data streams from vehicle systems and sensors410, 420. The ECM 205 may further have data processing capability tocollect and present vehicle data to the J-Bus 204 (which may allowtransmittal to the telematics device 102), and output standard vehiclediagnostic codes when received from a vehicle's J-Bus-compatibleon-board controllers 420 or vehicle sensors 410.

In one embodiment, the instruction data receiving port 207 may be one ofseveral components available in the telematics device 102. Embodimentsof the instruction data receiving port 207 may include an Infrared DataAssociation (IrDA) communication port, a data radio, and/or a serialport. The instruction receiving data port 207 may receive instructionsfor the telematics device 102. These instructions may be specific to thevehicle 100 in which the telematics device 102 is installed, specific tothe geographical area in which the vehicle 100 will be traveling, orspecific to the function the vehicle 100 serves within the fleet.

In one embodiment, a radio frequency identification (RFID) tag 212 maybe one of several components available for use with the telematicsdevice 102. One embodiment of the RFID tag 212 may include an activeRFID tag, which comprises at least one of the following: (1) an internalclock; (2) a memory; (3) a microprocessor; and (4) at least one inputinterface for connecting with sensors located in the vehicle 100 or thetelematics device 102. Another embodiment of the RFID tag 212 may be apassive RFID tag. One or more RFID tags 212 may be internal to thetelematics device 102, wired to the telematics device 102, and/orproximate to the telematics device 102. Each RFID tag 212 maycommunicate wirelessly with RFID interrogators within a certaingeographical range of each other. RFID interrogators may be locatedexternal to the vehicle 100.

In one embodiment, the data radio 209 may be one of several componentsavailable in the telematics device 102. The data radio 209 may beconfigured to communicate with a WWAN, WLAN, or WPAN, or any combinationthereof. In one embodiment, a WPAN data radio provides connectivitybetween the telematics device 102 and peripheral devices used in closeproximity to the vehicle 100, a local computer, a cellular telephone,and/or the like. As mentioned above, in one embodiment of the invention,a WPAN, such as, for example, a Bluetooth™ network (IEEE 802.15.1standard compatible) may be used to transfer information between thetelematics device 102 and a portable data acquisition device or aperipheral device. In other embodiments, WPANs compatible with the IEEE802 family of standards may be used. In one embodiment, the data radio209 may be a Bluetooth™ serial port adapter that communicates wirelesslyvia WPAN to a Bluetooth™ chipset located in a peripheral device. Inaddition, a Media Access Control (MAC) address, which is a code uniqueto each Bluetooth™-enabled device that identifies the device, similar toan Internet protocol address identifying a computer in communicationwith the Internet, can be communicated to other devices in communicationwith the WPAN, which may assist in identifying and allowingcommunication among vehicles, cargo, and portable data acquisitiondevices equipped with Bluetooth™ devices. As discussed above with regardto FIG. 2, and as one of ordinary skill in the art will readilyrecognize, other wireless protocols exist (e.g., cellular technology)and can likewise be used in association with embodiments of the presentinvention.

As described in greater detail below, in various embodiments, thetelematics device 102 may be configured to capture and store telematicsdata from the vehicle sensors 410 at predefined time intervals and inresponse to detecting the occurrence of one or more of a plurality ofpredefined vehicle events. Generally, a vehicle event may be defined asa condition relating to any parameter or combination of parametersmeasurable by the one or more vehicle sensors 410 (e.g., the engineidling, vehicle speed exceeding a certain threshold, etc.). As such, thetelematics device 102 may be configured to continuously monitor thevarious vehicle sensors 410 and detect when the data being generated byone or more the vehicle sensors 410 indicates one or more of theplurality of predefined vehicle events. In response to detecting avehicle event, the telematics device 102 captures data from all of thevehicle sensors 410 or a particular subset of the vehicle sensors 410associated with the detected vehicle event.

As an example, the telematics device 102 may be configured to recognizethe occurrence of a first vehicle event (e.g., the vehicle's 100 enginebeing turned on or off), a second vehicle event (e.g., the vehicle's 100speed exceeding a certain threshold), a third vehicle event (e.g., aseat belt in the vehicle 100 being engaged or disengaged), and/or afourth vehicle event (e.g., vehicle's 100 heading reaching a thresholdaway from center). In one embodiment, the telematics device 102 isconfigured to capture and store telematics data from all of the vehiclesensors 410 in response to detecting any of the first vehicle event, thesecond vehicle event, the third vehicle event, and/or the fourth event.In another embodiment, the telematics device 102 is further configuredsuch that the first vehicle event is associated with a first subset ofvehicle sensors (e.g., the seat belt sensor and location sensor), thesecond vehicle event is associated with a second subset of vehiclesensors (e.g., a vehicle speed sensor and location sensor), the thirdvehicle event is associated with a third subset of vehicle sensors(e.g., a seat belt sensor, engine speed sensor, and vehicle speedsensor), and the fourth vehicle event is associated with a fourth subsetof vehicle sensors (e.g., a heading sensor and a location sensor).Accordingly, in this embodiment, the telematics device 102 will captureand store telematics data from the first set of vehicle sensors afterdetecting the first vehicle event, the second set of vehicle sensorsafter detecting the second vehicle event, the third set of vehiclesensors after detecting the third vehicle event, and the fourth set ofvehicle sensors after detecting the fourth vehicle event.

The vehicle events programmed for recognition by the telematics device102 can be defined in a variety of ways. As will be appreciated from thedescription herein, the telematics device 102 may be configured tocapture telematics data in response to vehicle events defined by anycombination of conditions sensed by the vehicle sensors 410. Thesepredefined vehicle events may be stored, for example, on the telematicsdevice's memory modules 210, or on another data storage mediumaccessible by the telematics device's processor 201.

For example, in various embodiments, the telematics device 102 isconfigured to recognize vehicle events characterized by data generatedby on/off vehicle sensors. These vehicle events may include: (a) avehicle's engine being turned on, (b) a vehicle's engine being turnedoff, (c) a vehicle door opening, (d) a vehicle door closing, (e) avehicle door being locked, (f) a vehicle door being unlocked, (g) avehicle's reverse gear being selected, (h) a vehicle's one or moreforward drive gears being selected, (i) a vehicle's neutral or park gearbeing selected, (j) a vehicle's parking break being engaged, (k) avehicle's seat belt being engaged, (1) a vehicle's seat belt beingdisengaged, and any other event definable by a parameter measured by anon/off sensor.

In addition, various embodiments of the telematics device 102 are alsoconfigured to recognize vehicle events characterized by data generatedby variable voltage vehicles sensors or other types of dynamic vehiclesensors. These vehicle events may include (a) a vehicle's speedincreasing from standstill to a non-zero value, (b) a vehicle's speeddecreasing from a non-zero value to standstill, (c) a vehicle's enginespeed exceeding a certain threshold, (d) a vehicle's engine speeddropping below a certain threshold, (e) a vehicle beginning to move in areverse direction, (f) a vehicle ceasing to move in a reverse direction,(g) a vehicle's heading reaching a threshold away from center, (h) avehicle's engine temperature exceeding a certain threshold, (i) avehicle's gas level falling below a certain level, (j) a vehicle's speedexceeding a certain threshold, and any other event definable by aparameter measured by a variable voltage or other dynamic sensor.

In addition, various embodiments of the telematics device 102 are alsoconfigured to recognize vehicle events characterized by data generatedby GPS-sensors or other location sensing devices. These vehicle eventsmay include (a) a vehicle moving into a geo-fenced area (e.g., ageo-fenced area defining a shipping hub, delivery area, or other workarea), (b) a vehicle moving out of a geo-fenced area (e.g., a geo-fencedarea defining a shipping hub, delivery area, or other work area), (c) avehicle traveling onto a predefined route (e.g., a GPS-based roadroute), (d) a vehicle traveling off of a predefined route, (e) a vehicletraveling onto a known road (e.g., a road recognized by a GPS device),(f) a vehicle traveling off of a known road (e.g., exceeding a certainpredefined distance from a known road), and any other event definable bya parameter measured by a location sensing device.

According to various embodiments, the telematics device 102 may be alsoconfigured to recognize multiple unique vehicle events based on a singlevarying parameter measured by one of the vehicle sensors 410. As oneexample, the telematics device 102 may be configured such that a firstvehicle event is detected anytime the vehicle's speed begins to exceed50 miles-per-hour, while a second vehicle event is detected anytime thevehicle's speed begins to exceed 70 miles-per-hour. As such, thetelematics device 102 may capture telematics data from vehicle sensors410 in response to the vehicle 100 accelerating past 50 miles-per-hour,and again as the vehicle 100 accelerates past 70 miles-per-hour. Inaddition, as noted earlier, the telematics device 102 may capturetelematics data from unique subsets of vehicle sensors based on thevarying measurements of vehicle speed (e.g., a first subset of vehiclessensors associated with the 50-mph vehicle event and a second subset ofvehicle sensors associated with the 70-mph vehicle event). This conceptmay also be applied to other variable parameters sensed by vehiclesensors, such as vehicle heading (e.g., various threshold degrees fromcenter), engine speed (e.g., various threshold RPM measurements), andvehicle distance from a predefined path (e.g., threshold value for feetfrom a known road, vehicle route, or other GPS-based geographiclocation).

In addition, vehicle events may be defined by a combination ofconditions indicated by various vehicle sensors 410. For example, incertain embodiments, the telematics device 102 may be configured todetect instances of stationary vehicle engine idling (e.g., where theengine is on and the vehicle is not moving) based on a combination ofdata from a vehicle engine sensor and a vehicle speed sensor. In suchembodiments, a first vehicle event is defined as the vehicle 100 beingturned on and beginning to idle (e.g., instances in which the vehiclesensors 410 indicate the vehicle's engine is turned on and the vehiclespeed is zero), a second vehicle event is defined as the vehicle 100beginning to move and thereby ceasing to idle (e.g., instances in whichthe vehicle sensors 410 indicate the vehicle's engine is on and thevehicle's speed has increased from zero to a non-zero value), a thirdvehicle event is defined as the vehicle 100 slowing to a stop andbeginning to idle again (e.g., any instance in which the vehicle sensors410 indicate the vehicle's engine is on and the vehicle's speed hasdecreased from a non-zero value to zero), and a fourth vehicle event isdefined as the vehicle 100 being turned off and again ceasing to idle(e.g., any instance in which the vehicle sensors 410 indicate thevehicle's engine is turned off and the vehicle speed is zero). As aresult, in this embodiment, vehicle events are detected and telematicsdata is captured at the beginning and end of every period during whichthe vehicle's engine is idling. In various embodiments, the telematicsdevice 102 captures every period of engine idling for each deliveryvehicle. Other examples of vehicle events defined by a combination ofconditions include (a) where a vehicle seat belt is engaged ordisengaged while the vehicle is idling, (b) where a vehicle exceeds acertain speed while located within a certain geographic area associatedwith the certain speed, and (c) a vehicle door opening or closing whilethe engine is on.

In addition to—or as an alternative to—capturing telematics data inresponse to detected vehicle events, the telematics device 102 may befurther configured to automatically capture telematics data from thevehicle sensors 410 at predefined time intervals. For example, in oneembodiment, the telematics device 102 is programmed with a thresholddata capture time (e.g., one second, 10 seconds, one minute) and isconfigured to automatically capture telematics data from the vehiclesensors 410 where no vehicle events are detected for a period exceedingthe defined time. This configuration ensures that the threshold datacapture time is the longest possible duration between telematics databeing collected and ensures that the vehicle 100 is continuouslymonitored even through periods where none of the predefined vehicleevents are detected. As will be appreciated from the description herein,the threshold data capture time may be defined as any period of timeaccording to the preference of a fleet management system 5 user. Whereno vehicle events are defined, the telematics device 102 would thencapture telematics data from the vehicle sensors according to thethreshold data capture time interval as a default setting.

Although the telematics device 102 is described above as capturingtelematics data in response to detected vehicle events, or in responseto a certain elapsed time, the telematics device 102 may also beconfigured to capture telematics data in response to other occurrences.For example, the telematics device 102 may be triggered remotely fromthe central server to capture telematics data from all, or particular,vehicle sensors at any time.

As noted above, in response to a triggering event—such as a definedvehicle event or elapsed threshold data capture time—the telematicsdevice 102 captures telematics data from the vehicle sensors 410. In oneembodiment, the telematics device 102 is configured to store thecaptured telematics data in fields of one or more data records, eachfield representing a unique measurement or other data from a uniquevehicle sensor. As the telematics device 102 continues to capturetelematics data in response to triggering events, multiple records ofdata comprising multiples sets of concurrently captured telematics dataare amassed. The captured telematics data may be initially stored, forexample, in the telematics devices memory modules 201, in another datastorage component of the telematics device 102, or in a remote location(e.g., a cloud database).

In various embodiments, after capturing data from any of the vehiclesensors 410, the telematics device 102 may be further configured toconcurrently capture and store contextual data. The contextual data mayinclude, for example, the date (e.g., 12/30/10) and time (e.g., 13:24)the data was captured, the vehicle from which the data was captured(e.g., a vehicle identification number such as 16234), the driver of thevehicle from which the data was captured at the time it was captured(e.g., John Q. Doe), and/or a logged reason for the data capture (e.g.,a code indicating a detected vehicle event or indicating that thepredefined time interval had elapsed). The contextual data may becaptured, for example, from various telematics device components (e.g.,an internal clock) and from data stored on the telematics device 102(e.g., current driver name, current vehicle id, or various vehicle eventcodes). Further, the telematics device 102 may be configured toassociate the captured telematics data with the captured contextual datain order to ensure concurrently captured telematics data and contextualdata are linked. For example, in one embodiment, the telematics device102 stores concurrently captured telematics data and contextual data inthe same data record or records.

In various embodiments, a driver may be required to enter his or herdriver ID number (or name) and vehicle id number at the beginning ofeach day (e.g., using a portable data acquisition device incommunication with the telematics device 102) in order to enable thetelematics device 102 to associate telematics data captured that daywith accurate contextual data. In other embodiments, the telematicsdevice 102 may be programmed remotely (e.g., from the central server 120over the network 130) such that it is associated with the appropriatedriver and vehicle information. According to various embodiments, thecontextual data may be formatted in any computer-readable andtransmittable data format. For example, in one embodiment, thecontextual data is metadata. As the telematics data captured from thevarious vehicle sensors 410 is associated with the captured contextualdata, the central server 120 will later be able to search and identifystored telematics data based on—for example—a particular date, time,vehicle, driver, and/or vehicle event.

As noted above, the telematics device 102 is also configured to transmitcaptured telematics data and contextual data to the central server 120.According to various embodiments, the captured data may be transmittedusing any of the communication methods or protocols described herein, aswell as various other methods and protocols known in the art. Forexample, the telematics device 102 may be configured to first attempt toestablish a connection with the central server 120 (e.g., via a wirelesssignal). If a successful connection is made, the telematics device 102will transfer captured data to the central server 120. However, if asuccessful connection cannot be made, the telematics device may beconfigured to alternatively transfer data to a portable data acquisitiondevice (e.g., via a wireless signal or USB connection).

According to various embodiments, the defined vehicle events thattrigger the telematics device 102 to capture and store telematics data,the sensors 410 from which telematics data are captured, and theintervals defined for capturing and storing data when no vehicle eventsare detected each may impact the effectiveness with which the fleetmanagement system 5 is able to evaluate the captured telematics data.For example, capturing data from a large number of vehicle sensors at ahigh frequency may allow the fleet management system 5 to analyze thetelematics data with greater accuracy. This could be accomplished, forexample, by a fleet management system with many defined vehicle eventsand relatively short intervals for automatically capturing telematicsdata.

However, as some embodiments of the fleet management system 5 will havemore limited storage capacity for storing captured telematics data, theamount of telematics data collected may be regulated based on the systemvariables described above. For example, a system user that has limiteddata storage resources and that is particularly interested in monitoringseat belt usage in a fleet of vehicles may configure the telematicsdevices 102 of the fleet vehicles 100 to capture and store data fromonly those sensors relevant to seat belt status. In addition, the usermay configure the telematics devices 102 to capture data at the minimalfrequency necessary to accurately report seat belt usage. Thisembodiment could use, for example, a small number of vehicle events andlong time interval for capturing telematics data when no vehicle eventsare detected. As a contrasting example, a large fleet management entityhaving large amounts of data storage resources may configure thetelematics devices 102 of its large fleet of vehicles 100 to capture andstore data from a wide variety of vehicle sensors at a high frequencysuch that the telematics data may be analyzed to assess a wide varietyof vehicle and driver efficiencies. As described above, this embodimentcould use, for example, a large number of vehicle events and short timeinterval for automatically capturing telematics data. Accordingly, thetelematics device 102 may be flexibly configured to suit the needs of aparticular fleet management system 5 user.

Central Server

As noted above, various embodiments of the central server 120 aregenerally configured for receiving and storing operational data (e.g.,telematics data received from the telematics device 102) and evaluatingthe operational data for a fleet of vehicles in order to assess variousfleet efficiencies and aid fleet management system 5 users in improvingthe operational efficiency of the fleet. According to variousembodiments, the central server 120 includes various means forperforming one or more functions in accordance with embodiments of thepresent invention, including those more particularly shown and describedherein. As will be appreciated from the description herein, however, thecentral server 120 may include alternative devices for performing one ormore like functions without departing from the spirit and scope of thepresent invention.

FIG. 4 illustrates a schematic diagram of the central server 120according to various embodiments. The central server 120 includes aprocessor 60 that communicates with other elements within the centralserver 120 via a system interface or bus 61. In the illustratedembodiment, the central server 120 includes a display device/inputdevice 64 for receiving and displaying data. This display device/inputdevice 64 may be, for example, a keyboard or pointing device that isused in combination with a monitor. In certain embodiments, the centralserver 120 may not include a display device/input device and may bealternatively accessed by a separate computing device (e.g., a networkedworkstation) having a display device and input device. The centralserver 120 further includes memory 66, which preferably includes bothread only memory (ROM) 65 and random access memory (RAM) 67. Theserver's ROM 65 is used to store a basic input/output system 26 (BIOS),containing the basic routines that help to transfer information betweenelements within the central server 120.

In addition, the central server 120 includes at least one storage device63—such as a hard disk drive, a floppy disk drive, a CD Rom drive, oroptical disk drive—for storing information on various computer-readablemedia, such as a hard disk, a removable magnetic disk, or a CD-ROM disk.As will be appreciated by one of ordinary skill in the art, each ofthese storage devices 63 is connected to the system bus 61 by anappropriate interface. The storage devices 63 and their associatedcomputer-readable media provide nonvolatile storage for a personalcomputer. It is important to note that the computer-readable mediadescribed above could be replaced by any other type of computer-readablemedia known in the art. Such media include, for example, magneticcassettes, flash memory cards, digital video disks, and Bernoullicartridges.

A number of program modules may be stored by the various storage devicesand within RAM 65. In the illustrated embodiment, such program modulesinclude an operating system 80, a turn segment module 2000, an outlierreport module 3000, a summary report module 4000, a turn by turnanalysis module 5000, a turn type analysis module 6000, an intersectiontype analysis module 7000, and an intersection point module 8000.According to various embodiments, the modules 2000-8000 control certainaspects of the operation of the central server 120 with the assistanceof the processor 60 and operating system 80. Embodiments of thesemodules are described in more detail below in relation to FIGS. 6-23.

In a particular embodiment, these program modules 2000-8000, areexecuted by the central server 120 and are configured to generategraphical user interfaces accessible to users of the system. In oneembodiment, the user interfaces may be accessible via the Internet orother communications network. In other embodiments, one or more of themodules 2000-8000 may be stored locally on one or more computers andexecuted by one or more processors of the computers.

According to various embodiments, the central server 120 is configuredto send data to, receive data from, and utilize data contained in acentral server database, which may be comprised of one or more separate,linked databases. For example, in executing the various modules2000-8000, the central server 120 may retrieve data necessary forperforming various analyses from the central server database, and maystore data resulting from various analyses in the central serverdatabase. According to various embodiments, the central server databasemay be a component of the central server 120, or a separate componentlocated remotely from the central server 120. In addition, the centralserver database may be configured for storing data in various data sets.In various embodiments, each data set may comprise a plurality of storeddata records, each record (or set of associated records) comprising oneor more data fields of unique data entries. For example, telematics dataand contextual data concurrently captured by the telematics device 102may be stored in a data record, where each data field in the data recordrepresents a unique data entry (e.g., a measurement of vehicle speed,GPS coordinates, the time and date the data was captured, and an IDnumber of the vehicle from which the data was captured).

Also located within the central server 120 is a network interface 74,for interfacing and communicating with other elements of a computernetwork. It will be appreciated by one of ordinary skill in the art thatone or more of the central server 120 components may be locatedgeographically remotely from other central server 120 components.Furthermore, one or more of the components may be combined, andadditional components performing functions described herein may beincluded in the central server 120.

While the foregoing describes a single processor 60, as one of ordinaryskill in the art will recognize, the central server 120 may comprisemultiple processors operating in conjunction with one another to performthe functionality described herein. In addition to the memory 66, theprocessor 60 can also be connected to at least one interface or othermeans for displaying, transmitting and/or receiving data, content or thelike. In this regard, the interface(s) can include at least onecommunication interface or other means for transmitting and/or receivingdata, content or the like, as well as at least one user interface thatcan include a display and/or a user input interface. The user inputinterface, in turn, can comprise any of a number of devices allowing theentity to receive data from a user, such as a keypad, a touch display, ajoystick or other input device.

While reference is made to a central “server” 120, as one of ordinaryskill in the art will recognize, embodiments of the present inventionare not limited to a client-server architecture. The system ofembodiments of the present invention is further not limited to a singleserver, or similar network entity or mainframe computer system. Othersimilar architectures including one or more network entities operatingin conjunction with one another to provide the functionality describedherein may likewise be used without departing from the spirit and scopeof embodiments of the present invention. For example, a mesh network oftwo or more personal computers (PCs), or similar electronic devices,collaborating with one another to provide the functionality describedherein in association with the central server 120 may likewise be usedwithout departing from the spirit and scope of embodiments of thepresent invention.

Capturing Operational Data for a Fleet

According to various embodiments, the fleet management system 5 isconfigured to capture operational data from various delivery vehicles100 and their respective drivers over a period of time in order to amassdata reflecting the overall operations of the fleet. The operationaldata captured by the fleet management system 5 generally comprisesvehicle telematics data, which may be captured from various vehiclesensors by the telematics device 102. Generally, the telematics data isindicative of various vehicle dynamics (e.g., vehicle location, enginespeed, etc.).

As described in greater detail below, the telematics device 102 isconfigured for capturing telematics data such that the data may later beevaluated. The captured operational data is then transmitted to thecentral server 120, which receives, processes, and stores the data inorder to it prepare it for evaluation in accordance with user requestsreceived via a graphical user interface and/or for automatic analysis inaccordance with pre-determined analysis protocols.

Operation of Telematics Device Capturing Telematics Data

As noted above, according to various embodiments, the telematics device102 is generally configured to control various vehicle sensors 410positioned on a particular delivery vehicle 100, capture and storevehicle telematics data generated by those sensors 410, and transmit thetelematics data to the central server 120. FIG. 5 illustrates exemplarysteps executed by the telematics device 102 to capture and transmittelematics data according to one embodiment. In various embodiments, thecomponents of the telematics device 102 described herein may beconfigured to execute the steps of FIG. 5 in accordance with theprinciples described above.

Beginning with step 602, the telematics device 102 monitors datagenerated by the vehicle sensors 410 for parameters that matchpredefined vehicle events programmed in the telematics device 102. Inone embodiment, the telematics device 102 is programmed to monitor someor all the following predefined vehicle events in step 602: (a) thevehicle 100 being turned on and beginning to idle (e.g., where vehiclesensors 410 indicate the vehicle's engine is turned on and the vehiclespeed is zero), (b) the vehicle 100 beginning to move and therebyceasing to idle (e.g., where the vehicle sensors 410 indicate thevehicle's engine is on and the vehicle's speed has increased from zeroto a non-zero value), (c) the vehicle 100 slowing to a stop andbeginning to idle (e.g., where the vehicle sensors 410 indicate thevehicle's engine is on and the vehicle's speed has decreased from anon-zero value to zero), (d) the vehicle 100 being turned off andceasing to idle (e.g., where the vehicle sensors 410 indicate thevehicle's engine is turned off and the vehicle speed is zero), (e) thevehicle 100 moving out of a geo-fenced area associated with its homeshipping hub (e.g., as indicated by a GPS sensor), (f) the vehicle 100moving into a geo-fenced area associated with its home shipping hub, (g)the vehicle 100 moving into a geo-fenced area associated with a deliveryarea assigned to vehicle 100 and its driver, (h) the vehicle 100 movingout of a geo-fenced area associated with a delivery area assigned tovehicle 100 and its driver, (i) the vehicle 100 beginning to move in areverse direction, (j) the vehicle 100 ceasing to move in a reversedirection, (k) the vehicle's seat belt being engaged or disengaged whilethe vehicle's engine is on, and (l) the vehicle's heading changingbeyond a predefined threshold degree.

Next, at step 604, the telematics device 102 determines whether any ofthe aforementioned predefined vehicle events have occurred. If a vehicleevent is detected, the telematics device 102 moves to step 606, where itcaptures and stores telematics data from the vehicle sensors 410. Asnoted earlier, the telematics data captured from the sensors 410 willindicate measurements or data from each of the vehicle sensors 410. Thistelematics data may indicate, for example, engine ignition status (e.g.,on or off), engine speed (e.g., RPM), vehicle speed (e.g., miles perhour), vehicle location (e.g., latitude and longitude), current distancetraveled (e.g., current odometer reading), location status (e.g.,on-property, on-area), seat belt status (e.g., engaged or disengaged),and vehicle backing status (e.g., moving in reverse or not moving inreverse). In one embodiment, the telematics device 102 stores capturedtelematics data in its memory modules 210, in another data storagecomponent of the telematics device 102, or in an associated database(e.g., a cloud database).

If a vehicle event is not detected in step 604, the telematics device102 moves to step 608, where it determines whether a threshold datacapture time has elapsed. For example, in one embodiment, the thresholddata capture time is defined as 3 seconds. If the telematics device 102determines that the threshold data capture time has not elapsed, itreturns to step 602 to continue monitoring for vehicle events. However,if the telematics device 102 determines that the threshold data capturetime has elapsed (e.g., more than 3 seconds have passed since the lasttime data was captured from the vehicle sensors), the telematics device102 moves to step 606 and captures telematics data from all of thevehicle sensors 410 as described above.

Next, at step 612, the telematics device 102 captures contextual dataand associates the contextual data with the telematics data captured andstored in step 606. In various embodiments, step 612 may be executedconcurrently with the step 606. In one embodiment, the telematics device102 is configured to capture some or all of the following contextualdata in step 612: the date (e.g., 12/30/10) and time (e.g., 13:24) thedata was captured, the vehicle from which the data was captured (e.g., avehicle identification number such as 16234), the driver of the vehiclefrom which the data was captured at the time it was captured (e.g., JohnQ. Doe), and a logged reason for the data capture (e.g., a codeindicating the detected vehicle event or indicating that the thresholddata capture time interval elapsed). Further, in one embodiment, thetelematics device 102 is configured to associate the captured telematicsdata with the captured contextual data by storing fields of telematicsdata captured from the vehicles sensors 410 in the same record, orrecords, as concurrently captured contextual data, thereby associatingconcurrently captured data.

Next, at step 614, the telematics device 102 transmits the telematicsdata and associated contextual data captured and stored in steps 606 and612 to the central server 120. This may be accomplished by using any ofthe transmission methods and systems described herein, as well as othermethods, protocols, and systems known in the art. As described earlier,in one embodiment the telematics device 102 is configured to firstattempt to transmit captured data to the central server 120, andsubsequently attempt to transfer data to a portable data acquisitiondevice if a connection with the central server 120 is unavailable.

Operation of Central Server Processing Telematics Data

According to various embodiments, the central server 120 is configuredfor receiving, processing, and storing telematics data received from thetelematics device 102. In particular, the central server 120 processesand stores received telematics data in a manner that facilitates laterevaluation of the data.

According to various embodiments, in response to receiving inboundtelematics data, the central server 120 is configured to process andstore the data in an Operational Data Set stored on the central serverdatabase (which may comprise one or more separate, linked databases, andmay be a local or remote database). The central server 120 populates theOperational Data Set by storing telematics data in association withconcurrently captured contextual data, thereby providing a contextualrelationship between all of the stored operational data. For example, invarious embodiments, the Operational Data Set comprises a plurality ofdata records representing concurrently captured data. Each data record(or plurality of associated data records) comprises a plurality of datafields representing a unique data entry.

In one embodiment, a data record of telematics data may comprise aplurality of data fields each representing a measurement from thevehicle sensors 410 (e.g., vehicle speed, vehicle location, enginespeed, vehicle heading) and a plurality of data fields each representinga contextual data measurement (e.g., date, time, driver, vehicle, loggedreason for data capture). The data in each data field of the recordrepresents data captured concurrently with the data in the other datafields. By storing telematics data in association with contextual data,the central server 120 may later access and retrieve data from theOperational Data Set by searching the stored data according to date,time, driver, vehicle, logged reason for data capture, or any other datafield or combination of data fields associated with the storedtelematics data (e.g., engine speed, vehicle speed, RPM, etc.).

In addition, according to various embodiments, the central server 120 isconfigured for maintaining a Planning Data Set stored in the centralserver database (or in another database accessible by the central server120). The Planning Data set may include stored data indicating, forexample, planned delivery routes for various drivers and vehicles (e.g.,a GPS-based route plan for a particular delivery vehicle 100), thelocations of planned stops along each delivery route (e.g., locationname and/or GPS location), planned distances associated with planneddelivery routes and stops (e.g., total planned distance for a deliveryroute, planned distances between planned stops), planned timesassociated with various routes and stops (e.g., planned times for travelbetween stops, planned times for executing a delivery at a particularstop), planned delivery activities at each stop (e.g., pickup, delivery,pickup & delivery), particular packages or freight to be picked-up ordelivered at a given stop (e.g., one or more tracking numbers forpackages or freight), bills of lading associated with packages orfreight being picked up or delivered at a particular stop (e.g., anumber or code associated with a bill of lading), the weight of packagesor freight to be picked-up or delivered at a particular stop (e.g.,total weight for a pickup or delivery, or weight associated with aparticular bill of lading, package, or portion of freight), and thenumber of units to be picked up or delivered at each stop (e.g., totalnumber of units for a pickup or delivery, or number of units associatedwith a particular bill of lading).

The data stored in the Planning Data Set may be stored such that isassociated with, for example, a particular driver, delivery vehicle,route, date, and/or hub location. As such, the central server 120 mayaccess and retrieve data from the Planning Data Set by searching thestored data according to driver, vehicle, route, date, hub location, orany data field associated with the above described data (e.g., time,distance, weight, bill of lading number, tracking number, etc.).Accordingly, as described in greater detail below, the central server120 may retrieve planning data stored in the Planning Data Set for usein evaluating the operational data stored in the Operational Data Setand/or the central server 120 may retrieve operational data stored inthe Operational Data Set for use in evaluating planning data stored inthe Planning Data Set.

According to various embodiments, the central server 120 may be furtherconfigured to evaluate data stored in the Operational Data Set toidentify segments of activity indicated by the operational data (hereinreferred to as “segmenting” the data). For example, each identifiedactivity segment may represent a period of time (e.g., 11:00 to 11:42 on12/31/10) classified according to activity (e.g., engine idle segments,vehicle stop time, vehicle travel time), many of which may overlap withone another. According to various embodiments, these activity segmentsmay be identified by the central server 120 in accordance with theprinciples and configurations detailed in U.S. patent application Ser.No. 13/435,498 (now published as U.S. Publication No. 2012/0253888), theentirety of which is hereby incorporated by reference. In suchembodiments, the resulting segmented data may be stored in a SegmentedData Set for use in further evaluations or analyses performed by thecentral server 120.

In various embodiments, the central server 120 is particularlyconfigured to evaluate data stored in the Operational Data Set toidentify vehicle turn segments (e.g., periods of time during which theoperational data indicates a vehicle was making a turn) and determinevarious attributes of each vehicle turn. In various embodiments, theresulting turn segment data is stored in a Turn Segment Data Set of thecentral server database (which may be unique from, or a subset of, theaforementioned Segmented Data Set). As described in greater detailbelow, according to various embodiments, the central server 120 isconfigured to execute the above-referenced turn segment module 2000 inorder to segment the operational data stored in the Operational Data Setand generate turn segment data to be stored in the Turn Segment DataSet. For example, in one embodiment, the central server 120 isconfigured to execute the turn segment module 2000 at the end of eachbusiness day, segment the day's data added to the Operational Data Set,and add the resulting segmented data to the Turn Segment Data set. Invarious other embodiments, the central server 120 may be configured torun the turn segment module 2000 at other increments or in response to aspecific user request (e.g., a user request to segment a specific subsetof operational data in the Operational Data Set).

Turn Segment Module

As noted above, various embodiments of the turn segment module 2000 areconfigured for evaluating operational data in order to identify vehicleturn segments indicated by the data. Generally, each identified turnsegment represents a period of time during which a vehicle is making aturn from one road onto another road or a turn from one roadwaydirection on a road to another roadway direction on the same road, suchas a U-turn. For example, a given turn segment may begin at 11:45:09 AMon Dec. 24, 2011 when a driver begins to change a vehicle's heading tothe left in order to make a left-hand turn, and end at 11:45:31 AM onDec. 24, 2011 when the vehicle's left-hand turn is completed and thevehicle's heading has leveled out. By identifying turn segmentsreflected in the operational data captured by the telematics device 102,the turn segment module 2000 can generate an accounting of turns made byone or more vehicles within the fleet during one or more time periods.As described in relation to the various modules 3000-8000 below,identifying turn segments in the captured operational data for a fleetenables the central server 120 to perform a variety of further analysesin order to assess various fleet efficiencies and to provide a graphicalrepresentation of vehicle and delivery activities for any period oftime.

FIG. 6 illustrates steps executed by the turn segment module 2000 tosegment operational data according to one embodiment. Beginning at step2002, the turn segment module 2000 first selects operational data fromthe Operational Data Set to segment for turn-identification. As notedabove, the central server 120 may call the turn segment module 2000 tosegment newly captured (or previously unsegmented) operational datastored in the Operational Data Set with a predefined frequency (e.g., atthe end of every business day) or in response to a user request (e.g., arequest received via the user interface to segment operational datacorresponding to certain user-selected parameters). Accordingly, theturn segment module 2000 executes step 2002 according to these frequencyor user request parameters (e.g., by identifying unsegmented data in theOperational Data Set or by retrieving operational data corresponding touser-specified parameters).

Next, at step 2004 the turn segment module 2000 assesses data points inthe selected operational data to identify instances in which a vehiclehas made a turn. For example, in certain embodiments, the turn segmentmodule 2000 is configured to identify instances in which a particularvehicle's heading deviates by a threshold heading value (or more)between consecutive data points. In one embodiment, the turn segmentmodule 2000 accomplishes this by comparing the GPS location ofsuccessive data points to assess changes in heading (e.g., starting withthe first data point in the data selected in step 2002 and proceedinguntil all data points have been assessed).

To illustrate this concept, FIG. 7 shows an intersection of two roads R1and R2. As the vehicle travels along road R1, its telematics device 102captures a series of intermittent data points 301-307 (e.g., at apredefined interval as discussed above), which are depicted in FIG. 7according to their respective GPS locations. As shown in FIG. 7, as thevehicle travels north on road R1, there is no significant change inheading between the first three data points 301, 302, 303. However, atthe fourth data point 304, the vehicle has deviated from its previousheading (indicated by a dashed line) by a first angle θ1. Similarly, theheadings between the fourth, fifth, and sixth data points 304-306continue to change as the vehicle makes a right-hand turn (as indicatedby angles θ2 and θ3). At the seventh data point 307, the vehicle'sheading stabilizes as it travels east down road R2 away from theintersection. Accordingly, for each data point 301-307, the turn segmentmodule 2000 is configured to determine the change in heading bycalculating the angle between the vehicle's current heading and itsprevious heading. Where this angle exceeds the predefined thresholdheading value (e.g., 30 degrees), the current data point is marked inthe operational data as a turn point.

Using this approach, the turn segment module's logic can be manipulatedto suit various applications. For example, the threshold heading valuecan be adjusted to eliminate false turn identifications or may bevariable (e.g., based on the route or region associated with theanalyzed operational data). Additionally, according to certainembodiments, the threshold heading value may be defined as a change inheading spanning multiple data points (e.g., a deviation of 45 degreesor more across four or less data points). In such an embodiment, wherethe change in heading between adjacent data points does not meet orexceed the threshold heading value, the turn segment module 2000 may beconfigured to sum changes in heading across a predefined number of datapoints and determine whether the aggregate heading change meets orexceeds the threshold heading value. In further embodiments, thethreshold heading value may be defined as a change in heading over apredefined period of time (e.g., a change in heading of greater than 30degrees in less than four seconds). In such an embodiment, the turnsegment module 2000 may be configured to sum changes in heading acrossthe data points captured within the predefined period preceding thecurrent data point and determine whether the aggregate heading changemeets or exceeds the threshold heading value.

In other embodiments, the turn segment module 2000 may identify turnpoints by comparing vehicle heading data (e.g., heading data capturedfrom a heading sensor, such as a digital compass) for adjacent datapoints. In such an embodiment, if the vehicle heading data associatedwith a current point differs from the vehicle heading data associatedwith the preceding data point by the threshold heading value (or more),the turn segment module 2000 marks the current data point as anidentified turn point. As above, this calculation could also beperformed over a predefined number of data points or multiple datapoints spanning a particular time period. As will be appreciated fromthe description herein, the turn segment module 2000 can be configuredto evaluate the user-selected operational data to identify turn pointsin a variety of ways depending on the data available.

Referring back to FIG. 6, the turn segment module 2000 next proceeds tostep 2006 where it determines whether the current data point has beenmarked as a turn point based on the analysis performed in step 2004. Ifthe current data point is not a turn point, the turn segment module 2000returns to step 2004 and analyzes the next data point in theuser-selected operational data. If the current data point has beenmarked as a turn point, the turn segment module 2000 continues to step2008.

As multiple data points are typically captured over the course of avehicle turn, the turn segment module 2000 next identifies in step 2008the data points associated with the beginning and end of the vehicle'sturn in order to define a full turn segment. According to variousembodiments, the turn segment module 2000 may be configured to identifythese beginning and end points based on vehicle heading, vehicle speed,distance traveled, engine speed (e.g., idle time) and/or other suitableparameters. For example, using the turn point marked in step 2004 as abase, the turn segment module 2000 first analyzes data points precedingthe marked turn point to identify the beginning of the turn. In oneembodiment, this may be accomplished in two stages. In the first stage,the turn segment module 2000 analyzes prior data points by assessingchanges in heading to determine the beginning of a turn (i.e., the pointat which the vehicle began to change its heading to make the identifiedturn). In the second stage, analyzes further prior data points byassessing changes in speed or distance to determine whether there wasadditional time prior to the beginning of the turn itself that is stillattributable to the turn (e.g., where a vehicle is stopped at a light,stop sign, or in a traffic queue prior to making the turn).

For example, in the illustration of FIG. 7, the change in heading θ1 maybe below the threshold heading value, while the change in heading θ2 mayexceed the threshold. In this case, the turn segment module 2000 marksthe data point 305 as the turn point. The turn segment module 2000 thenassesses the immediately preceding data point 304 and determines whetherit represents a change in heading. Because the data point 304 representsa change in heading of θ1, the turn segment module 2000 determines theidentified turn was in progress at data point 304. The turn segmentmodule 2000 then assesses the next preceding data point 303 anddetermines that no change in heading (or a comparatively minor change inheading) was made up to that point. Accordingly, the turn segment module2000 preliminarily marks data point 303 as the beginning turn pointbecause it is the last data point before a significant change in headingwas detected.

Turning to the second stage of the analysis, in one embodiment, the turnsegment module 2000 assesses the next preceding data point 302 anddetermines the distance of the data point 302 from the data point 303(e.g., using the GPS data associated with the data points). In theexample of FIG. 7, the data point 302 is a significant distance (e.g.,20 meters) from the data point 303, and so the turn segment module 2000determines that the vehicle was not stopped or moving slowly betweendata points 302 and 303. As such, the turn segment module 2000 confirmsthe data point 303 as the beginning of the turn segment.

However, if the data point 302 had been at the same location as the datapoint 303—or at a location a short distance from the data point 303—theturn segment module 2000 would have marked the data point 302 as the newpreliminary beginning turn point because the data would indicate thevehicle was stopped or waiting in traffic prior to beginning its changein heading to the make the identified turn. The turn segment module 2000would have then moved to the next preceding data point 301 and performedthe same analysis. By repeatedly performing this analysis until asignificant distance between data points is identified, the turn segmentmodule 2000 is able to identify the true beginning point of the turn(i.e., not simply when the vehicle began to change its heading to makethe turn, but when the vehicle's travel was significantly affected as aresult of its need to make the identified turn).

In other embodiments, the turn segment module 2000 may be configured toassess vehicle speed or engine speed data (in addition to or in place ofdistance) to perform the second stage of the analysis. For example, ifthe speed of the vehicle at the data point preceding the preliminarybeginning turn point was zero or near zero, the turn segment module 2000would recognize that the vehicle was stopped or slowly moving in trafficat that point and—because it immediately precedes the preliminarybeginning turn point 303—would then mark it as the new preliminarybeginning turn point. In this case, the turn segment module 2000 wouldthen perform the same analysis on the next preceding data point 301 todetermine if the vehicle was stopped or moving slowly. Once the turnsegment module 2000 identifies a preceding data point indicating thevehicle is moving at significant speed (or indicating the engine speedis significantly above idle), the turn segment module 2000 wouldrecognize the current preliminary beginning turn point as the truebeginning turn point.

After identifying the true beginning turn point, the turn segment module2000 next analyzes data points succeeding the marked turn point toidentify the ending of the turn. In various embodiments, this may beaccomplished using a methodology similar to that employed to identifythe beginning turn point. For example, in one embodiment, the turnsegment module 2000 analyzes later data points by assessing changes inheading to identify the ending of the turn (i.e., the point at which thevehicle ceases changing its heading and has completed the identifiedturn). Referring back to the illustration of FIG. 7 as an example, theturn segment module 2000 would first identify data point 306 as the nextdata point after the identified turn point 305. In this example, thedata point 306 represents a change in heading of θ3 from the vehicle'sheading at the turn point 305. Accordingly, the turn segment module 2000considers data point 306 a part of the turn segment and proceeds toassess the next data point 307. As shown in FIG. 7, there is nosignificant change in the vehicle's heading between data points 306 and307. Accordingly, the turn segment module 2000 is able to recognize thatdata point 307 is not a part of the turn segment (i.e., the turn hasalready been completed at the location associated with this data point).Accordingly, the turn segment module 2000 marks data point 306 as theending turn point because it is the last data point representing asignificant change in heading.

In certain embodiments, the turn segment module 2000 may be furtherconfigured to execute a second stage of the ending point analysis byaccessing data points succeeding the ending turn point to determinewhether the vehicle has stopped at the end of the turn or slowed intraffic (e.g., using the same analysis principles described above inrelation to determining the true beginning point of the turn). Accordingto the preference of the system user, this second stage analysis may beomitted for the identification of one, or both of, the beginning turnpoint and ending turn point (e.g., where the user is only interested inidentifying turn instances and is not concerned with the duration ofindividual turns).

After identifying the beginning and ending points of the turn segment,the turn segment module completes step 2008 by storing the beginning andending points in a Turn Segment Data Set as being associated with aindividually identified turn segment (e.g., in the central serverdatabase). In addition, in one embodiment, the identified turn segmentis stored in the Turn Segment Data Set in association with contextualdata indicating the operational data from which it was derived. Forcontext, FIG. 8 shows a Gantt chart type illustration of the turnsegment identified based on the travel of the vehicle shown in FIG. 7.

Referring back to FIG. 6, at step 2010, the turn segment module 2000next determines the location, time, and duration of the current turnsegment and stores this information in the Turn Segment Data Set. Forexample, in one embodiment, the location of the turn segment isidentified via GPS or other location data associated with the markedturn point (e.g., data point 305 in FIG. 7). In certain embodiments, mapdata may be accessed to identify the location of the turn segment bystreet names associated with the intersection where the turn occurred(e.g., in addition to or in place of identifying the location of theturn by GPS coordinates or the like). The contextual data stored inassociation with the telematics data is also used to identify a timeassociated with the turn segment. For example, in one embodiment, theturn segment module 2000 identifies the time stamp associated with themarked turn point and associates this time as the time of the turnsegment's occurrence (e.g., 11:45:19 AM on Dec. 24, 2011). Theidentified time is stored in association with the turn segment data inthe Turn Segment Data Set. The turn segment module 2000 also calculatesthe duration of the turn segment based on the time of occurrence of thebeginning and ending turn points identified in step 2008 (e.g., the timeelapsed between these) and stores this duration in the Turn Segment DataSet. For example, if the identified beginning turn point was captured at11:45:09 AM and the identified ending turn point was captured at11:45:31, then the duration of the turn segment is 22 seconds.

Accordingly, in one embodiment, the duration for a given turn segmentwould include both time during which the vehicle was traveling toexecute the turn and time during which the vehicle was idling (e.g., notmoving in traffic, either waiting to execute the turn or in the middleof the turn). In certain embodiments, however, the turn segment module2000 may be configured to separate idle turn time (e.g., time during aturn segment in which the vehicle was idling) and travel turn time(e.g., time during a turn segment in which the vehicle is moving) foreach turn segment. In such embodiments, one or more of the lateranalysis modules 3000-8000 may be configured to perform analogousanalyses based only on idle turn time or travel turn time, as opposed tofull turn durations.

Next, at step 2018, the turn segment module 2000 identifies the turntype for the current turn segment and stores this information in theTurn Segment Data set. For example, a given turn segment may represent aright-hand turn, a left-hand turn, or a turn-around (e.g., a U-turn). Inone embodiment, the turn segment module 2000 determines the turn type ofthe current turn segment based on the GPS locations of the data pointscomprising the turn segment (e.g., turn points heading north and thenveering east indicate a right hand turn). In another embodiment, theturn segment module 2000 determines the turn type of the current turnsegment based on vehicle heading data associated with the data pointscomprising the turn segment (e.g., where a heading change of +45° to+135° is a right hand turn, a heading change of −45° to −135° is a lefthand turn, and a heading change of +135° to 180° or −135° to 180° is aturn-around). Upon classifying the turn segment as a left-hand turn,right-hand turn, or turn-around, the turn segment module 2000 stores theclassification in the Turn Segment Data Set.

In certain embodiments, the turn segment module 2000 may also beconfigured to identify turn-around turns occurring in conjunction with aback-up event (e.g., a period of time in which the vehicle was moving inreverse). For example, in one embodiment, the turn segment module 2000may accomplish this by reviewing the telematics data captured proximatein time to the occurrence of an identified turn-around turn (e.g.,within 45 seconds of the turn-around turn occurrence) and determinewhether a back-up event was recorded by the telematics device duringthis window. Where the turn segment module 2000 determines that aturn-around turn is associated with a back-up event, the turn type maybe stored as “turn-around with backup.”

Next, at step 2020, the turn segment module 2000 identifies the type ofintersection where the turn segment occurred. For example, in certainembodiments, the turn segment module 2000 refers to the GPS of locationof an identified turn segment (e.g., the GPS location of the segment'sturn point) and identifies the roads intersecting at that location. Theturn segment module 2000 then refers to map data in the central serverdatabase to determine the intersection type. The determined intersectiontype may be, for example, a yield sign intersection, a stop signintersection, a roundabout, a traffic light intersection, a cul-de-sac,or an off/on-ramp. Upon classifying the intersection type for the turnsegment, the turn segment module 2000 stores the classification in theTurn Segment Data Set.

In certain embodiments, the turn segment module 2000 is furtherconfigured to associate the turn segment directly with underlying mapdata. For example, the turn segment module 2000 may be configured torefer to underlying map data in which roads are defined by a pluralityof road segments extending between node points (i.e., points at whichthe road segments defining the roads intersect). In such embodiments,the turn segment module 2000 may be configured to identify the nearestnode point in the underlying map data to each data point comprising anidentified turn segment in order to associate the turn segment with themap data. As an example, for the turn segment defined by data points303-306 in FIG. 7, the turn segment module 2000 would identify thenearest node point in underlying map data to each of the data points303-306, thereby associating the full turn segment with one or more nodepoints and road segments in the underlying map data. In otherembodiments, the turn segment module 2000 may be configured to simplyassociate the identified turn point in the turn segment with the nearestnode point in the underlying map data, thereby associating the turnsegment with a single node in the underlying map data. In associatingthe turn segments with the underlying map data, the turn segment module2000 can also be configured associate the turn segments with theappropriate street segment ids stored in the underlying map data (e.g.,such that a turn segment is associated with the road(s) on which itoccurs based on the underlying map data).

According to various embodiments, the turn segment module 2000 may alsobe further configured to execute additional steps to meet thepreferences of a particular user. For example, as noted above, thetelematics device 102 may be configured to detect when the vehicle 100has entered or exited a particular geographic area, such as a geo-fencedarea defining the shipping hub. Accordingly, in one embodiment, the turnsegment module 2000 is further configured to review operational data andidentify data indicating instances in which the vehicle 100 has enteredor departed a predefined geographical area. As a result, the turnsegment module 2000 can be configured to analyze turns made within ageo-fenced area or outside of a geo-fenced area separately. For example,in certain embodiments a user may want to assess only turns occurringwithin a particular geo-fenced delivery area (e.g., a residentialneighborhood), which the turn segment module 2000 may be configured toaccomplish.

As a result of the foregoing steps, the turn segment module 2000 is ableto populate the Turn Segment Data Set with data records eachcorresponding to an identified turn segment. For example, in oneembodiment, each turn segment data record comprises a turn pointlocation and time, a beginning turn point location and time, an endingpoint location and time, a turn segment location (e.g., GPScoordinates), a turn segment time, a turn segment duration, a turnsegment type, a turn intersection type, a turn intersection point (e.g.,the roads intersecting at the turn point), a turn segment driver, a turnsegment vehicle ID, a turn segment route ID, and a turn segment hublocation (e.g., the shipping hub from which the vehicle associated withthe turn segment departed).

Central Server User Interface

As described above, the central server 120 is configured for evaluatingoperational data (e.g., telematics data and contextual data) for a fleetof vehicles in order to assess various fleet efficiencies and aid fleetmanagement system 5 users in improving the operational efficiency of thefleet. According to various embodiments, the central server's 120evaluation of operational data is conducted in accordance with userinstructions received via the central server's user interface. Invarious embodiments, the user interface is a graphical user interfaceaccessible from a remote workstation (e.g., in communication with thecentral server 120 via the network 130), or by using the centralserver's display device/input device 64. For example, in variousembodiments, a user may log in to the fleet management system 5 from aremote workstation (e.g., by opening a log-in page and entering a userid and password using a workstation display and keyboard). The centralserver 120 may be configured to recognize any such log-in request,verify that user has permission to access the system (e.g., byconfirming the user id and password are valid), and present the userwith a graphical user interface (e.g., displayed on the workstation'smonitor).

FIG. 9 illustrates a start-up user interface 800 according to oneembodiment. In the illustrated embodiment, the start-up user interface800 includes an interactive geographical map display 810, a locationmenu 811, a date selection field 812, a route selection menu 813, adriver selection menu 814, a vehicle selection menu 815, an outlierreport button 830, a summary report button 832, a turn by turn analysisbutton 834, a turn type analysis button 836, an intersection typeanalysis button 838, an intersection point analysis button 839, and arun analysis button 819.

According to various embodiments, the map and menus 810-815 allow asystem user to specify various telematics data attributes in order toselect certain turn segment data for evaluation by the central server120. In various embodiments, any combination of selections made from themap and menus 810-815 will dictate the turn segment data loaded andanalyzed by the central server 120. For example, in one embodiment, theuser may request evaluation of only turn segment data relating to aparticular vehicle route by selecting a route from the route selectionmenu 813. Likewise, the user may request evaluation of only turn segmentdata relating to a particular vehicle by selecting a vehicle ID from thevehicle selection menu 815 and may request evaluation of only turnsegment data relating to vehicles operated by a particular driver byselecting a driver from the driver selection menu 814. As an example,where both a route and vehicle have been selected, the central server120 would load only turn segment data relating to the selected vehiclewhile traveling along the selected route.

Furthermore, a user may request evaluation only of operational datacaptured on a particular date or range of dates by selecting a desireddate or date range (as well as specific time of day associated with anyselected date) using the date section field 812. The user also has theoption of requesting evaluation of operational data for all routesstemming from a particular location (e.g., by selecting only one or moreshipping hub locations from the location menu 811), or for all routes atall locations on a particular date (e.g., by selecting only a date ordate range using the date selection field 812). Moreover, a user mayrequest evaluation of turn segment data relating to a particulargeographical area by selecting an area on map display 810 (e.g., byusing a mouse to select a two-dimensional geographical area on the mapdisplay 810). The map display 810 may also include tools for zooming inon various portions of the illustrated route, selecting a specificintersection for further analysis, and/or the like. As will beappreciated from the description above, the user may request evaluationof all operational data or any subset of operational data defined by anycombination of parameters provided in the map/menus 810-815.

After selecting operational data to be evaluated, the user may select aparticular type of turn analysis to be performed by the central server120. As described in greater detail below, in one embodiment, thecentral server 120 is configured to analyze the user-selected turnsegment data to generate an outlier report, a summary report, a turn byturn analysis, a turn type analysis, an intersection type analysis, andan intersection point analysis. Each of these analyses may be requestedby a user by selecting the corresponding one of the analysis typebuttons 830-839 on the start-up interface 800. After the user-selecteddata and analysis type has been defined using the map/menus 810-815 andanalysis type buttons 830-839, the user may select the run analysisbutton 819 in order to trigger the user requested analysis by thecentral server 120.

According to various embodiments, the central server 120 is configuredto detect a user's selection of the various parameters and optionspresented on the user interface 800 and call one or more of the softwaremodules 2000-8000 in order to perform the appropriate data evaluation.FIG. 10 illustrates exemplary steps executed by the central server 120in order to respond to user evaluation requests received via the userinterface 800. Beginning at step 902, the central server 120 monitorsthe user interface 800 for user input (e.g., selection of the variousmenus and buttons 810-839). Next, at step 904, the central server 120determines whether the user has requested an analysis of particular turnsegment data (e.g., by selecting the run analysis button 819). If theuser has not requested that an analysis be performed, the central server120 moves back to step 902, where it continues to monitor the userinterface 800 for user input. If the user has requested that a turnanalysis be performed, the central server 120 moves to step 906.

At step 906, the central server 120 identifies the turn segment datacorresponding to the user's selections from the map/menus 810-815 on theuser interface. For example, in one embodiment, the central server 120reviews the turn segment data in the Turn Segment Data Set andidentifies the appropriate data based on the contextual data in eachturn segment data record. According to various embodiments, the centralserver 120 reviews the turn segment time field to identify segmentsoccurring on a particular date/time, the turn segment location field toidentify segments within a particular geographic location, the turnsegment route field to identify segments relating to a particularvehicle route, the turn segment driver field to identify segmentsrelating to a particular driver, and the turn segment vehicle field toidentify turn segments relating to a particular vehicle. In certainembodiments, where the user selects the intersection point analysisbutton 839, the central server 120 is configured to prompt the user toselect an intersection from the map display 810 (or by entering atextual description of the intersection) and retrieve turn segment datacorresponding to that particular location (e.g., based on the locationfield in the turn segment data records). After identifying the turnsegment data corresponding to the user's request, the central server 120loads the identified turn segment database for analysis by one or moreof the modules 3000-8000 (e.g., by retrieving the data from the TurnSegment Data Set in the central server database and loading it in thecentral server's memory).

Next, at step 908, the central server 120 runs the analysis modulecorresponding to the user's selection on the user interface 800. Forexample, if user selects the outlier report button 830 the centralserver 120 will run the outlier report module 3000, if the user selectsthe summary report button 832 the central server 120 will run thesummary report module 4000, if the user selects the turn by turnanalysis button 834 the central server 120 will run the turn by turnanalysis module 5000, if the user selects the turn type analysis button836 the central server 120 will run the turn type analysis module 6000,if the user selects the intersection type analysis button 838 thecentral server 120 will run the intersection type analysis module 7000,and if the user selects the intersection point analysis button 839 thecentral server 120 will run the intersection point analysis module 8000.A detailed description of the functionality and steps executed by eachof the modules 3000-8000 now follows.

Outlier Report Module

According to various embodiments, the outlier report module 3000 isconfigured to analyze the user-selected turn segment data and identifyoutlier turn segments having an abnormal duration. For example, FIG. 11illustrates exemplary steps executed by the outlier report module 3000in order to identify outlier turn segments and provide an interactivedisplay of the same to a user. Beginning at step 3002, the outlierreport module 3000 displays an outlier report graphical user interface(“GUI”). FIG. 12 shows an outlier report graphical user interface 801according to one embodiment. As shown in FIG. 12, the outlier report GUI801 includes a map display 810, analysis buttons 830-839 (e.g., the sameas those provided on the start-up user interface 800), a data table 850,data table sorting buttons 851, a duration filter menu 861, a turn typefilter menu 862, a filter by map button 863, current data indicators840, and a return to data selection button 865.

Next, at step 3004, the outlier report module 3000 analyzes the turnsegment data loaded by the central server 120 and identifies outlierturn segments based on defined outlier criteria. For example, in oneembodiment the outlier report module 3000 is configured such that theoutlier criteria comprises any turn exceeding one minute in duration. Insuch an embodiment, the outlier report module 3000 would execute step3004 by analyzing the loaded turn segment data, identifying all turnsegments exceeding one minute in duration, and marking these turnsegments as outlier turn segments. However, according to variousembodiments, the outlier criteria may be defined based on any conditionssuitable for a particular user. For example, in another embodiment, auser may define the outlier criteria as (i) any left-hand turnsexceeding one minute in duration, (ii) any right-hand turns exceeding 30seconds in duration, and (iii) any turn-around turns exceeding 45seconds in duration. In such an embodiment, the outlier report module3000 would review the turn segments in the loaded turn segment datacorresponding to each turn type (e.g., right-hand, left-hand,turn-around) and identify those turn segments meeting the outliercriteria. As will be appreciated from the description herein, thecentral server 120 may be configured to enable to the user to modify andset any outlier criteria for use by the outlier report module 3000 inexecuting step 3004.

Next, at step 3006, the outlier report module 3000 displays theidentified outlier turn segments in the data table 850 on the outlierreport GUI 801. For example, in the illustrated embodiment, the outlierreport module 3000 populates the data table 850 with the chronologicalturn number, the location, the turn type, and duration of eachidentified outlier turn segment. In addition, the current dataindicators 840 show the route, driver, and/or vehicle associated withthe currently analyzed user-selected data.

As shown in FIG. 12, the outlier turn segments are initially ordered inthe data table 850 according to duration, with the highest-durationoutlier turn segment being listed first. However, the order of theoutlier turn segments displayed in the data table 850 may be changed inaccordance with a user selection of one of the data table sortingbuttons 851, which include the turn number, location, turn type, andduration. For example, where the user selects the turn number sortingbutton, the outlier report module 3000 will sort the outlier turnsegments in the data table 850 chronologically in the order ofoccurrence. Similarly, where the user selects the turn type sortingbutton, the outlier report module 3000 will group the outlier turnsegments in the data table 850 according to their turn type.

Additionally, turn segments displayed in the data table 850 can befiltered using the duration filter menu 861, the turn type filter menu862, and the filter by map button 863. For example, in response to userinput received via the duration filter menu 861, the outlier reportmodule 3000 will display only outlier turn segments having a durationwithin a range specified by the user. Similarly, in response to userinput received via the turn type filter menu 862, the outlier reportmodule 3000 will display only outlier turn segments of a turn typematching one or more turn types specified by the user. Additionally, inresponse to selection of the filter by map button 863, the outlierreport module 3000 enables a user to select a geographical area in themap display 810 and will then display only outlier turn segmentsoccurring within the user-defined map area.

Next, at step 3008, the outlier report module 3000 plots the travel path(or paths) 2100 of the vehicle (or vehicles) associated with the outlierturn segments and the location of the outlier turn segments on the mapdisplay 810. For example, in one embodiment, the outlier report module3000 executes step 3008 by first loading and displaying a baseelectronically navigable map (herein the “base map”). In variousembodiments, the data comprising the base map may be stored on, andretrieved from, the central server database. Next, the outlier reportmodule 3000 reviews operational data corresponding to the user-selectedparameters and identifies location data (e.g., captured GPS coordinates)and time data (e.g., captured times, such as 09:38:12) associated witheach data record in the corresponding operational data.

The outlier report module 3000 next generates a graphical representationof the travel path of each vehicle associated with user selected data onthe map display 810. In one embodiment, the outlier report module 3000accomplishes this by plotting each individual location data point in theloaded operational data on the map display 810 and then connecting theplotted location points in chronological order—based on the retrievedtime data—with lines displayed over the base map. In various embodimentsthe travel path(s) generated by the outlier report module 3000 may eachcomprise colored line(s) having a thickness greater than that of roadsshown in the base map and which include arrows disposed along the travelpath(s) to indicate the direction of each vehicle's 100 travel.Additionally, the outlier report module 3000 plots the location of eachoutlier turn segment on the map display 810 to provide geographicalcontext to each outlier segment.

As will be appreciated from the foregoing description, the outlierreport GUI 801 generated by the outlier report module 3000 provides aclear display of turn segments having an abnormally long duration andenables the user to assess turns causing inefficiencies in vehiclerouting. Once the outlier report module 3000 has executed the stepsshown FIG. 11, the user may return to the start-up interface 800 byselecting the return to data selection button 865, or request adifferent analysis of the currently selected data by selecting one ofthe analysis type buttons 830-839.

Summary Report Module

According to various embodiments, the summary report module 4000 isconfigured to analyze the user-selected turn segment data and provide anoverall summary of turn statistics for the user-selected data. Forexample, FIG. 13 illustrates exemplary steps executed by the summaryreport module 4000 in order to provide an interactive display of turnstatistics to a user. Beginning at step 4002, the summary report module4000 displays a summary report graphical user interface. FIG. 14 shows asummary report graphical user interface 802 according to one embodiment.As shown in FIG. 14, the summary report GUI 802 includes a map display810, analysis buttons 830-839 (e.g., the same as those provided on thestart-up user interface 800), a data table 850, a duration filter menu861, a turn type filter menu 862, a filter by map button 863, currentdata indicators 840, and a return to data selection button 865.

Next, at step 4004, the summary report module 4000 analyzes the turnsegment data loaded by the central server 120 and calculates a pluralityof turn statistics based on the loaded turn segment data. For example,in one embodiment the summary report module 4000 is configured tocalculate the following statistics: (i) the total number of turnsindicated in the loaded turn segment data; (ii) the average duration ofall turns indicated in the loaded turn segment data; (iii) the averagenumber of turns per mile traveled for the loaded turn segment data; (iv)the total number of outlier turns indicated in the loaded turn segmentdata (e.g., using the techniques described above in relation to theoutlier report module 3000); (v) the average duration of all outlierturns indicated in the loaded turn segment data; and (vi) the percentageof all turns qualifying as outlier turn segments in the loaded turnsegment data. As will be appreciated from the description herein, thesummary report module 4000 may be configured to execute thesecalculations based on the relevant fields in each turn segment datarecord contained in the loaded turn segment data. Additionally,according to various other embodiments, the summary report module 4000may be configured to calculate any additional relevant statistics basedon the loaded turn segment data.

Next, at step 4006, the summary report module 4000 displays thecalculated turn statistics in the data table 850 on the summary reportGUI 802. In addition, the current data indicators 840 show the route,driver, and/or vehicle associated with the currently analyzeduser-selected data. As shown in FIG. 14, the turn statistics displayedin the data table 850 can be recalculated based on filtered data usingthe duration filter menu 861, the turn type filter menu 862, and thefilter by map button 863. For example, in response to user inputreceived via the duration filter menu 861, the summary report module4000 will recalculate the turn statistics for only turns having aduration within a range specified by the user. Similarly, in response touser input received via the turn type filter menu 862, the summaryreport module 4000 will recalculate the turn statistics for only turnshaving a turn type matching one or more turn types specified by theuser. Additionally, in response to selection of the filter by map button863, the summary report module 4000 enables a user to select ageographical area in the map display 810 and will then recalculate theturn statistics based only on turn segments occurring within theuser-defined map area.

Next, at step 4008, the summary report module 4000 plots the travel path(or paths) 2100 of the vehicle (or vehicles) associated with theuser-selected turn segments on the map display 810 (e.g., using thetechniques described above in relation to the outlier report module3000). As will be appreciated from the foregoing description, thesummary report GUI 802 generated by the summary report module 4000provides a clear display of turn statistics for the user-selected dataand enables the user to quickly assess the overall turn efficiency ofroutes, drivers, or vehicles associated with the analyzed data. Once thesummary report module 4000 has executed the steps shown FIG. 13, theuser may return to the start-up interface 800 by selecting the return todata selection button 865, or request a different analysis of thecurrently selected data by selecting one of the analysis type buttons830-839.

Turn by Turn Analysis Module

According to various embodiments, the turn by turn analysis module 5000is configured to analyze the user-selected turn segment data andgenerate a turn by turn report for the user-selected data. For example,FIG. 15 illustrates exemplary steps executed by the turn by turnanalysis module 5000 in order to provide an interactive display of turnsegments indicated by the user-selected data. Beginning at step 5002,the turn by turn analysis module 5000 displays a turn by turn graphicaluser interface. FIG. 16 shows a turn by turn graphical user interface803 according to one embodiment. As shown in FIG. 16, the turn by turnGUI 803 includes a map display 810, analysis buttons 830-839 (e.g., thesame as those provided on the start-up user interface 800), a data table850, data table sorting buttons 851, a duration filter menu 861, a turntype filter menu 862, a filter by map button 863, current dataindicators 840, and a return to data selection button 865.

Next, at step 5004, the turn by turn analysis module 5000 analyzes theturn segment data loaded by the central server 120 and displays eachturn segment indicated by the data in chronological order in the datatable 850. For example, in the illustrated embodiment, the turn by turnanalysis module 5000 populates the data table 850 with the chronologicalturn number, the location, the turn type, and duration of each turnsegment. In addition, the current data indicators 840 show the route,driver, and/or vehicle associated with the currently analyzeduser-selected data.

As shown in FIG. 16, the turn segments are initially ordered in the datatable 850 chronologically in order of occurrence, with the first turnsegment being listed first. However, the order of the turn segmentsdisplayed in the data table 850 may be changed in accordance with a userselection of one of the data table sorting buttons 851, which includethe turn number, location, turn type, and duration. For example, wherethe user selects the duration sorting button, the turn by turn analysismodule 5000 will sort the turn segments in the data table 850sequentially in order of high duration to shortest duration, therebyproviding user visibility to the longest turn segments indicated by theloaded data. As an exemplary illustration of this, FIG. 17 shows theturn by turn GUI 803 with the data table 850 sorted according toduration. Similarly, where the user selects the turn type sortingbutton, the turn by turn analysis module 5000 will group the turnsegments in the data table 850 according to their turn type.

Additionally, turn segments displayed in the data table 850 can befiltered using the duration filter menu 861, the turn type filter menu862, and the filter by map button 863. For example, in response to userinput received via the duration filter menu 861, the turn by turnanalysis module 5000 will display only turn segments having a durationwithin a range specified by the user. Similarly, in response to userinput received via the turn type filter menu 862, the turn by turnanalysis module 5000 will display only turn segments of a turn typematching one or more turn types specified by the user. Additionally, inresponse to selection of the filter by map button 863, the turn by turnanalysis module 5000 enables a user to select a geographical area in themap display 810 and will then display only turn segments occurringwithin the user-defined map area.

Next, at step 5006, the turn by turn analysis module 5000 plots thetravel path (or paths) 2100 of the vehicle (or vehicles) associated withthe user-selected turn segments on the map display 810 (e.g., using thetechniques described above in relation to the outlier report module3000). As will be appreciated from the foregoing description, the turnby turn GUI 803 generated by the turn by turn analysis module 5000provides a clear display of turn segments for the user-selected data andenables the user to quickly view and compare attributes of each of theseturns to assess the turn efficiency of routes, drivers, or vehiclesassociated with the analyzed data. Once the turn by turn analysis module5000 has executed the steps shown FIG. 15, the user may return to thestart-up interface 800 by selecting the return to data selection button865, or request a different analysis of the currently selected data byselecting one of the analysis type buttons 830-839.

Turn Type Analysis Module

According to various embodiments, the turn type analysis module 6000 isconfigured to analyze the user-selected turn segment data and determinestatistics for turns of each turn type (e.g., left turns, right turns,and turn-around turns) indicated in the data. For example, FIG. 18illustrates exemplary steps executed by the turn type analysis module6000 in order to classify turn segments in the loaded data according toturn type and provide an interactive display of turn statistics for eachturn type to a user. Beginning at step 6002, the turn type analysismodule 6000 displays an turn type graphical user interface. FIG. 19shows a turn type graphical user interface 805 according to oneembodiment. As shown in FIG. 19, the turn type GUI 805 includes a mapdisplay 810, analysis buttons 830-839 (e.g., the same as those providedon the start-up user interface 800), a data table 850, a data chart 855,current data indicators 840, and a return to data selection button 865.

Next, at step 6004, the turn type analysis module 6000 analyzes the turnsegment data loaded by the central server 120 and bins the turn segmentsin the data according to turn type (e.g., by reviewing the turn typefield in each turn segment data record and storing the turns in separateturn type logical bins). Next, at step 6006, the turn type analysismodule 6000 calculates turn statistics based on the loaded turn segmentdata for each turn type. For example, in one embodiment the turn typeanalysis module 6000 is configured to calculate the followingstatistics: (i) the total number of turns indicated in the loaded turnsegment data; (ii) the total number of left turns indicated in theloaded turn segment data; (iii) the total number of right turnsindicated in the loaded turn segment data; (iv) the total number ofturn-around turns indicated in the loaded turn segment data; (v) theaverage duration of all turns indicated in the loaded turn segment data;(vi) the average duration of all left turns indicated in the loaded turnsegment data; (vii) the average duration of all right turns indicated inthe loaded turn segment data; and (viii) the average duration of allturn-around turns indicated in the loaded turn segment data.

Additionally, the turn type analysis module 6000 may be configured tocalculate the number of turn segments of each turn type having aduration falling within predefined ranges. For example, in oneembodiment, the turn type analysis module 6000 is configured todetermine the number of left turns, right turns, and turn-around turnshaving a duration of 0-20 seconds, 21-30 seconds, 31-40 seconds, 41-50seconds, 51-60 seconds, 61-70 seconds, 71-80 seconds, 81-90 seconds, 91to 100 seconds, 101-110 seconds, 111-120 seconds, 121-130 seconds, andmore than 130 seconds, respectively. As will be appreciated from thedescription herein, the turn type analysis module 6000 may be configuredto execute these calculations based on the relevant fields in each turnsegment data record contained in the loaded turn segment data.Additionally, according to various other embodiments, the turn typeanalysis module 6000 may be configured to calculate any additionalrelevant statistics based on the loaded turn segment data.

Next, at step 6008, the turn type analysis module 6000 displays thecalculated turn statistics in the data table 850 and the data chart 855on the turn type GUI 805. For example, as shown in FIG. 19, the datatable 850 shows the number of and average of duration of left turns,right turns, turn-around turns, and total turns. Additionally, the datachart 855 provides a histogram illustrating the number of turns of eachturn type falling within each of the aforementioned duration ranges. Inaddition, the current data indicators 840 show the route, driver, and/orvehicle associated with the currently analyzed user-selected data.

Next, at step 6010, the turn type analysis module 6000 plots the travelpath (or paths) 2100 of the vehicle (or vehicles) associated with theuser-selected turn segments on the map display 810 (e.g., using thetechniques described above in relation to the outlier report module3000). As will be appreciated from the foregoing description, the turntype GUI 805 generated by the turn type analysis module 6000 provides aclear display of turn statistics for turns of each turn type and enablesthe user to assess the overall turn efficiency of routes, drivers, orvehicles associated with the analyzed data. Once the turn type analysismodule 6000 has executed the steps shown FIG. 18, the user may return tothe start-up interface 800 by selecting the return to data selectionbutton 865, or request a different analysis of the currently selecteddata by selecting one of the analysis type buttons 830-839.

Intersection Type Analysis Module

According to various embodiments, the intersection type analysis module7000 is configured to analyze the user-selected turn segment data anddetermine statistics for turns of each intersection type (e.g., yieldsign, stop sign, traffic light, across traffic, turn-around) indicatedin the data. For example, FIG. 20 illustrates exemplary steps executedby the intersection type analysis module 7000 in order to classify turnsegments in the loaded data according to intersection type and providean interactive display of turn statistics for each intersection type toa user. Beginning at step 7002, the intersection type analysis module7000 displays an intersection type graphical user interface. FIG. 21shows an intersection type graphical user interface 806 according to oneembodiment. As shown in FIG. 21, the intersection type GUI 806 includesa map display 810, analysis buttons 830-839 (e.g., the same as thoseprovided on the start-up user interface 800), a data table 850, a datachart 855, current data indicators 840, and a return to data selectionbutton 865.

Next, at step 7004, the intersection type analysis module 7000 analyzesthe turn segment data loaded by the central server 120 and bins the turnsegments in the data according to intersection type (e.g., by reviewingthe intersection type field in each turn segment data record and storingthe turns in separate intersection type logical bins). Next, at step7006, the intersection type analysis module 7000 calculates turnstatistics based on the loaded turn segment data for each intersectiontype. For example, in one embodiment the intersection type analysismodule 7000 is configured to calculate the following statistics: (i) thetotal number of turns indicated in the loaded turn segment data; (ii)the total number of turns occurring at a yield sign intersection in theloaded turn segment data; (iii) the total number of turns occurring at astop sign intersection in the loaded turn segment data; (iv) the totalnumber of turns occurring at a traffic light intersection in the loadedturn segment data; (v) the total number of turns occurring acrosstraffic (e.g., without a stop sign, yield sign, or traffic light) in theloaded turn segment data; (vi) the total number of turn-around turns notoccurring at a traffic sign or light in the loaded turn segment data;(vii) the average duration of all turns indicated in the loaded turnsegment data; (viii) the average duration of turns occurring at a yieldsign intersection in the loaded turn segment data; (ix) the averageduration of turns occurring at a stop sign intersection in the loadedturn segment data; (x) the average duration of turns occurring at atraffic light intersection in the loaded turn segment data; (xi) theaverage duration of turns occurring across traffic (e.g., without a stopsign, yield sign, or traffic light) in the loaded turn segment data; and(xii) the average duration of turn-around turns not occurring at atraffic sign or light in the loaded turn segment data.

Additionally, the intersection type analysis module 7000 may beconfigured to calculate the number of turn segments of each intersectiontype having a duration falling within predefined ranges. For example, inone embodiment, the intersection type analysis module 7000 is configuredto determine the number of yield sign intersection turns, stop signintersection turns, traffic light intersection turns, across trafficturns, and turn-around turns having a duration of 0-20 seconds, 21-30seconds, 31-40 seconds, 41-50 seconds, 51-60 seconds, 61-70 seconds,71-80 seconds, 81-90 seconds, 91 to 100 seconds, 101-110 seconds,111-120 seconds, 121-130 seconds, and more than 130 seconds,respectively. As will be appreciated from the description herein, theintersection type analysis module 7000 may be configured to executethese calculations based on the relevant fields in each turn segmentdata record contained in the loaded turn segment data. Additionally,according to various other embodiments, the intersection type analysismodule 7000 may be configured to calculate any additional relevantstatistics based on the loaded turn segment data.

Next, at step 7008, the intersection type analysis module 7000 displaysthe calculated turn statistics in the data table 850 and the data chart855 on the intersection type GUI 806. For example, as shown in FIG. 21,the data table 850 shows the number of and average of duration of yieldsign intersection turns, stop sign intersection turns, traffic lightintersection turns, across traffic turns, turn-around turns, and allturns. Additionally, the data chart 855 provides a histogramillustrating the number of turns of each intersection type fallingwithin each of the aforementioned duration ranges. In addition, thecurrent data indicators 840 show the route, driver, and/or vehicleassociated with the currently analyzed user-selected data.

Next, at step 7010, the intersection type analysis module 7000 plots thetravel path (or paths) 2100 of the vehicle (or vehicles) associated withthe user-selected turn segments on the map display 810 (e.g., using thetechniques described above in relation to the outlier report module3000). As will be appreciated from the foregoing description, theintersection type GUI 806 generated by the intersection type analysismodule 7000 provides a clear display of turn statistics for turnsoccurring at each intersection type and enables the user to assess theoverall turn efficiency of routes, drivers, or vehicles associated withthe analyzed data. Once the turn intersection type analysis module 7000has executed the steps shown FIG. 20, the user may return to thestart-up interface 800 by selecting the return to data selection button865, or request a different analysis of the currently selected data byselecting one of the analysis type buttons 830-839.

Intersection Point Analysis Module

According to various embodiments, the intersection point analysis module8000 is configured to analyze turn segment data relating to a particularuser-selected intersection and determine statistics for turns occurringat the intersection. For example, FIG. 22 illustrates exemplary stepsexecuted by the intersection point analysis module 8000 in order toanalyze turn segments in the loaded data occurring at the user-selectedintersection and provide an interactive display of statistics for therelated turns to a user. Beginning at step 8002, the intersection pointanalysis module 8000 displays an intersection point analysis graphicaluser interface. FIG. 23 shows an intersection point analysis graphicaluser interface 807 according to one embodiment. As shown in FIG. 23, theintersection point GUI 807 includes a map display 810, analysis buttons830-839 (e.g., the same as those provided on the start-up user interface800), a data table 850, a data chart 855, current data indicators 846,and a return to data selection button 865.

As discussed above in relation to step 906 executed by the centralserver 120 in FIG. 10, where the user selects the intersection pointanalysis button 839, the central server 120 is configured to prompt theuser to select an intersection from the map display 810 (or by enteringa textual description of the intersection) and retrieve turn segmentdata corresponding to that particular location. Accordingly, at step8004, the intersection point analysis module 8000 next analyzes theloaded turn segment data relating to the user-selected intersection andbins the turn segments in the data according to the time of day in whichthey occurred (e.g., by reviewing the time of occurrence field in eachturn segment data record and storing the turns in separate time of daylogical bins).

Next, at step 8006, the intersection point analysis module 8000calculates turn statistics based on the loaded turn segment data forsequential periods of time. For example, in one embodiment the turnintersection point analysis module 8000 is configured to calculate theaverage duration of all vehicle turns occurring at the user-selectedintersection for 30 minutes increments during the day (e.g., the averageduration of turns occurring at the user-selected intersection between7:30 AM and 8:00 AM, the average duration of turns occurring at theuser-selected intersection between 8:00 AM and 8:30 AM, and so forth).As will be appreciated from the description herein, the intersectionpoint analysis module 8000 may be configured to execute thesecalculations based on the relevant fields in each turn segment datarecord contained in the loaded turn segment data. Additionally,according to various other embodiments, the intersection point analysismodule 8000 may be configured to calculate any additional relevantstatistics based on the loaded turn segment data.

Next, at step 8008, the intersection point analysis module 8000 displaysthe calculated turn statistics in the data table 850 and the data chart855 on the intersection point GUI 807. For example, as shown in FIG. 23,the data table 850 shows the average duration of turns occurring at theuser-selected turn during each time-period band. Additionally, the datachart 855 provides a line graph illustrating the change in average turnduration at the user-selected intersection over the various time bands.

Next, at step 8010, the intersection point analysis module 8000 displaysthe user-selected intersection on the map display 810 and (whereapplicable) along with the intersection name 844 and provides anindication of the turn direction 3100 taken by vehicles at theintersection. In addition, current data indicators 846 provideadditional information associated with the intersection (e.g., route,intersection type, etc.).

As will be appreciated from the foregoing description, the intersectionpoint GUI 807 generated by the intersection point analysis module 8000provides a clear display of turn statistics for turns occurring at auser-selected intersection and enables the user to assess the overallefficiency of turns executed at the selected intersection. Once theintersection point analysis module 8000 has executed the steps shownFIG. 22, the user may return to the start-up interface 800 by selectingthe return to data selection button 865, or request a different analysisof the currently selected data by selecting one of the analysis typebuttons 830-839.

CONCLUSION

As should be appreciated, the embodiments may be implemented in variousways, including as methods, apparatus, systems, or computer programproducts. Accordingly, the embodiments may take the form of an entirelyhardware embodiment or an embodiment in which a processor is programmedto perform certain steps. Furthermore, the various implementations maytake the form of a computer program product on a computer-readablestorage medium having computer-readable program instructions embodied inthe storage medium. Any suitable computer-readable storage medium may beutilized including hard disks, CD-ROMs, optical storage devices, ormagnetic storage devices.

The embodiments are described below with reference to block diagrams andflowchart illustrations of methods, apparatus, systems, and computerprogram products. It should be understood that each block of the blockdiagrams and flowchart illustrations, respectively, may be implementedin part by computer program instructions, e.g., as logical steps oroperations executing on a processor in a computing system. Thesecomputer program instructions may be loaded onto a computer, such as aspecial purpose computer or other programmable data processing apparatusto produce a specifically-configured machine, such that the instructionswhich execute on the computer or other programmable data processingapparatus implement the functions specified in the flowchart block orblocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the functionality specified in theflowchart block or blocks. The computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions that execute on the computer or otherprogrammable apparatus provide operations for implementing the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport various combinations for performing the specified functions,combinations of operations for performing the specified functions andprogram instructions for performing the specified functions. It shouldalso be understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions oroperations, or combinations of special purpose hardware and computerinstructions.

Many modifications and other embodiments of the invention set forthherein will come to mind to one skilled in the art to which theseembodiments of the invention pertain having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is to be understood that the embodiments of the inventionare not to be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of the appended claims. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

That which is claimed:
 1. A system for assessing turns made by at leastone vehicle, said system comprising: one or more memory storage areas;and one or more processors in communication with said one or more memorystorage areas; wherein said processors are, collectively, configured to:receive, from one or more vehicle telematics devices located on the atleast one vehicle, vehicle telematics data indicative of a travel pathof the vehicle during one or more time periods, wherein the vehicletelematics data comprises a plurality of telematics data points, eachtelematics data point comprising data indicative of a vehicle heading ata particular location along the travel path of the vehicle and a timethe data point is generated; identify, based at least in part on saidvehicle telematics data, one or more turns executed by the vehicleduring the one or more time periods, the one or more turns eachcomprising instances in which the vehicle executes a turn in order tochange from (i) traveling in a first roadway direction on a first roadto (ii) traveling on a second road or traveling in a second roadwaydirection on the first road, wherein the one or more turns are eachidentified as comprising a change in vehicle heading between successivetelematics data points of the plurality of telematics data pointsexceeding a predefined threshold heading value; determine for eachidentified turn a turn segment comprising: a beginning turn pointcomprising a telematics data point occurring before the successivetelematics data points; an ending turn point comprising a telematicsdata point occurring after the successive telematics data points; thetime elapsed between the beginning turn point and ending turn point,wherein the time elapsed defines the duration of the turn segment; andan intersection type where the identified turn segment occurs by:identifying, based at least in part on a telematics data pointcorresponding to the identified turn segment, a location of the turnsegment; comparing the location of the turn segment against map data toidentify one or more roads intersecting at the location of the turnsegment; and determining, based at least in part on the one or moreroads intersecting at the location of the turn segment, an intersectiontype for the turn segment; receive a user request for analysis of turnscorresponding to one or more identified intersection types; identify,based at least in part on telematics data corresponding to each turnsegment, those turn segments occurring at one of the identifiedintersection types; and generate, based on said identified turnsegments, a graphical display comprising a map illustrating the locationof the identified turn segments and displaying one or more turn segmentattributes of said identified turn segments.
 2. The system of claim 1,wherein the beginning turn point is associated with a time and vehiclelocation at which the vehicle began executing a respective turn and theending turn point is associated with a time and vehicle location atwhich the vehicle completed executing the respective turn.
 3. The systemof claim 1, wherein the processors are configured to determine for eachturn segment the time of the turn segment's occurrence, the location ofthe turn segment's occurrence, and the duration of the turn segment, andto store each turn segment in association with data indicating the timeof the turn segment's occurrence, the location of the turn segment'soccurrence, and the duration of the turn segment.
 4. The system of claim3, wherein said processors are configured to determine the direction ofeach turn segment and classify each turn segment as representing a rightturn, left turn, or turn-around turn accordingly.
 5. The system of claim1, wherein said processors are configured to identify, among the turnsegments, outlier turn segments having a duration exceeding a thresholdduration.
 6. The system of claim 1, wherein said graphical displaycomprises a list of one or more of said identified turn segments.
 7. Thesystem of claim 6, wherein said list of one or more of said identifiedturn segments includes an data indicating one or more turn segmentattributes selected from the group consisting of: turn segment duration,turn segment type, turn segment location, and turn segment chronologicalnumber.
 8. The system of claim 6, wherein said list of one or more ofsaid identified turn segments is sorted according to turn segmentduration.
 9. The system of claim 6, wherein said list of one or more ofsaid identified turn segments is sorted chronologically in order of turnsegment occurrence.
 10. The system of claim 6, wherein the processorsare configured to identify those of said identified turn segmentsrepresenting left turns and wherein said list of one or more of saididentified turn segments comprises only said identified turn segmentsrepresenting left turns and is sorted according to the duration of saididentified turn segments representing left turns.
 11. The system ofclaim 1, wherein the processors are configured to determine the averageduration of the identified turn segments and wherein said one or moreturn segment attributes comprise said determined average duration of theidentified turn segments.